Public bug reported:
I can see that the slapd apparmor profile goes 90% of the way to working
out of the box with letsencrypt/certbot, but fails to include
abstractions/ssl_keys. The attached patch should work support all the
methods in these abstractions, and should be the default with the slapd
I have been attempting to preseed install 19.10 (eoan) and discovered
that this fix has not yet made its way into Ubuntu yet. Does anyone have
any idea when the fix is likely to make it in? Would be nice if it was
available in LTS (18.04) as well.
If you are quick enough to edit
/lib/partman/displ
After applying the above patch; either reboot, or regenerate /var/lib
/update-notifier/fsck-at-boot as follows:
$ sudo -s
# run-parts --lsbsysinit /etc/update-motd.d > /var/run/motd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
I was affected by this and bug and discovered that it appears to be
caused when the file /var/lib/update-notifier/fsck-at-reboot has a
datestamp in the future. This will never rectify itself unless the
actual date passes the datestamp on the file.
The attached patch fixes the problem.
** Patch ad
*** This bug is a duplicate of bug 747090 ***
https://bugs.launchpad.net/bugs/747090
@Serge,
Sorry for the delay. I am sure the kernel update will fix the issue. I
have however been running 2.6.38-8 with a custom patch to fix an issue
with LXC (https://bugzilla.kernel.org/show_bug.cgi?id=3123
After some further investigation, this bug appears to be a qemu-kvm bug.
I installed the lucid version of qemu-kvm, downgraded the domain
definition as follows:
[...]
hvm
^
[...]
And the domain now suspends and resumes reliably.
--
I've been trying this out every time a new version of Ubuntu is coming up for
release, and it has never worked! However, this is the most promising result
that I have seen to date. Maverick version of virt-manager seems to be able to
correctly save the running state to a file, however it prompts
** Attachment added: "Video of symptom..."
https://bugs.launchpad.net/bugs/771227/+attachment/2089833/+files/26-04-2011%2013-42-35.avi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771227
Title:
Public bug reported:
Description:Ubuntu 11.04
Release:11.04
libvirt-bin:
Installed: 0.8.8-1ubuntu6
Candidate: 0.8.8-1ubuntu6
Version table:
*** 0.8.8-1ubuntu6 0
500 http://gb.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
100 /var/lib/dpkg/status
You cre
In terms of testing, the auto-builds version seems to be working fine
for me with this fix...
--
mythfrontend.real crashed with SIGSEGV in
QX11PixmapData::x11ConvertToDefaultDepth()
https://bugs.launchpad.net/bugs/549593
You received this bug notification because you are a member of Ubuntu
Bugs,
I also had problems with eclipse hanging after I upgraded from karmic to
lucid. After reading comment #2, I saw that I I had xulrunner-1.9.1
installed and removed it. I have not had any issues since.
--
Eclipse hangs occasionally in Ubuntu Lucid
https://bugs.launchpad.net/bugs/574945
You received
I've not seen this issue recently. I'm guessing that it's been fixed
upstream at some point over the last few months. The bug can be closed.
Regards,
Paul.
--
WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281
ieee80211_scan_completed+0xcf/0x3f0 [mac80211]()
https://bugs.launchpad.n
On current lucid beta this device:
Bus 001 Device 004: ID 7392:7711
Works perfectly after blacklisting rt2800usb
--
Karmic RC tries to load rt2870sta AND rt2800usb. Results in no WiFi
https://bugs.launchpad.net/bugs/460323
You received this bug notification because you are a member of Ubuntu
Bu
Sorry,
I attached the wrong build log :( (you might have noticed its called
gvfs...). The correct one is now attached.
Testing
As with the Debian package, I have installed and tested on a USB stick -
since the installation needs to compile and load the ipheth kernel
module.
My guess is that
** Attachment added: "Install Log"
http://launchpadlibrarian.net/43777406/ipheth-install.log
--
FFe: Sync ipheth 1.0-1 (universe) from Debian sid (main)
https://bugs.launchpad.net/bugs/558946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "Build Log"
http://launchpadlibrarian.net/43777259/gvfs_1.4.2-0ubuntu1-amd64-20091205-1213
--
FFe: Sync ipheth 1.0-1 (universe) from Debian sid (main)
https://bugs.launchpad.net/bugs/558946
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi.
Please find the attached logs:
- Build log is produced by sbuild on a clean lucid debootstrap.
- Install log is produced on the same LVM chroot:
- dpkg -i ipheth*.deb.
- apt-get install -f to install failed dependencies.
--
FFe: Sync ipheth 1.0-1 (universe) from Debian sid (main)
https:
has unfortunately taken time to find a Debian Developer
willing to sponsor it, but ipheth has now been sponsored! The package has
passed NEW, and should now be available to sync.
All changelog entries:
ipheth (1.0-1) unstable; urgency=low
* Initial release (Closes: #566313)
-- Paul McEnery
I've built and installed version 2.10 and have been through a couple of
reboot cycles and everything on the NFS front appears to be working
correctly now.
On the first boot however, I noticed that the boot stalled while it was
supposedly doing an fsck. To my surprise, I was able to ssh to the
syst
I've done some further testing to ensure that mounting the DVD while
mythtv is running does not cause any adverse effects. No unexpected
behaviour has arisen as a result of applying the patch. I've updated the
upstream bug report asking if the patch can be committed to the 0.23
branch.
--
mythfro
I have tested the patch in the referenced upstream bug, and can confirm
that it solves the problem!
--
mythfrontend.real crashed with SIGSEGV in
QX11PixmapData::x11ConvertToDefaultDepth()
https://bugs.launchpad.net/bugs/549593
You received this bug notification because you are a member of Ubuntu
** Attachment added: "mythtv_build_fail.txt"
http://launchpadlibrarian.net/42502881/mythtv_build_fail.txt
--
Missing build dependency on mythtv source package
https://bugs.launchpad.net/bugs/551769
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: mythtv
Latest mythbuntu 0.23 package appears to be missing a build dependency.
Install build deps with:
apt-get build-dep mythtv
dpkg-buildpackage fails with the attached.
** Affects: mythtv (Ubuntu)
Importance: Undecided
Status: New
--
** Attachment added: ".var.log.mythtv.mythfrontend.log.txt"
http://launchpadlibrarian.net/42169939/.var.log.mythtv.mythfrontend.log.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/42169940/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian
** Visibility changed to: Public
--
mythfrontend.real crashed with SIGSEGV in
QX11PixmapData::x11ConvertToDefaultDepth()
https://bugs.launchpad.net/bugs/549459
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is still a problem on 9.10. Following this guide results in a
document that doesn't work as described.
http://wiki.services.openoffice.org/wiki/Documentation/How_Tos/Calc:_SUBTOTAL_function
Attached is an example document saved in .ods format on 9.10 with a
single formula.
Most people switc
Seems like some sort of differentiation is needed between mythvideo for
the frontend, and mythvideo for the backend.
The postinst script for mythvideo appears to create
/home/mythtv/.mythtv. On one of my frontend systems I've simply deleted
/home/mythtv/.mythtv as its not needed on a frontend. Har
I have built the latest CVS snapshot to overcome this issue (in the
short term), and its available in my PPA:
https://launchpad.net/~pmcenery/+archive/ppa
--
tv_grab_uk_rt (xmltv) fails when updating listings
https://bugs.launchpad.net/bugs/471372
You received this bug notification because you a
Public bug reported:
Binary package hint: beagle
Beagle is not indexing my Tomboy notes on Karmic. I have noticed that
the location of the notes has moved from ~/.tomboy to
~/.local/share/tomboy. I suspect this may have something to do with it.
I therefore added a path of ~/.local/share/tomboy to
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/34845163/AlsaDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34845164/BootDmesg.txt
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/34845165/Card0.Amixer.valu
Public bug reported:
Problem occurred on resume from a S3 suspend.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx
I can also confirm this behaviour. I updated from Jaunty to Karmic (I
assume beta at this point), and I have the following configuration:
$ sudo fdisk -l
===
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sect
On 15/06/2009, agent 8131 wrote:
>
> [...]
>
> A quick fix might be to symlink /etc/monitrc to /etc/monit/monitrc
> though I have not tested that.
>
IIRC from my testing, this does NOT work. Monit checks that the file
is in fact a file and not a link before starting up.
--
monit cannot find d
This looks like at upstream bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479357
A fix appears to have been released Is it possible for this fix to
be implemented in the Ubuntu package?
--
monit cannot find default monitrc on Intrepid
https://bugs.launchpad.net/bugs/292183
You recei
No. I tried both the LVDS- and TV-out quirk fixes with no success. The
problem appears to be the missing TMDS-2 output. When I disable the LVDS
output, X fails to start altogether with "No Screens". The TMDS-1 output
is the DVI port which seems to work when the TV is connected.
I have now reverted
** Attachment added: "lspci-vvnn.txt"
http://launchpadlibrarian.net/20621294/lspci-vvnn.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/20621295/Dependencies.txt
** Attachment added: "LsMod.txt"
http://launchpadlibrarian.net/20621296/LsMod.txt
** Attachment ad
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I have a mythtv frontend system installed on a Jetway J9F2-Extreme
motherboard which features an onboard HDMI port:
http://www.jetway.com.tw/jetway/system/productshow.asp?id=404&proname=J9F2-Extreme
I usually use the system with
I downloaded the source package for the version that comes with hardy,
replaced the source with 0.12.0 and recompiled. Synchronisation is
_much_ better now. I havent had any lock issues.
Thanks Sandy. Works a treat so far!
Sorry no package for everyone else. I dont have a proper build
environment
** Description changed:
Sorry. I cant find where this bug really belongs, so I have posted it
here hoping that it can be moved to the appropriate place.
The places menu is dynamically updated when media such as CD/DVD's and
USB sticks are inserted. When you select File -> Save As from a
** Attachment added: "save_as.png"
http://launchpadlibrarian.net/16086449/save_as.png
--
Places list in "Save As" not up to date
https://bugs.launchpad.net/bugs/249020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Attachment added: "places.png"
http://launchpadlibrarian.net/16086438/places.png
--
Places list in "Save As" not up to date
https://bugs.launchpad.net/bugs/249020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Public bug reported:
Sorry. I cant find where this bug really belongs, so I have posted it
here hoping that it can be moved to the appropriate place.
The places menu is dynamically updated when media such as CD/DVD's and
USB sticks are inserted. When you select File -> Save As from any
applicatio
I also have this problem on a Dell Inspiron 9300. It has the ATI
Mobility Radeon X300 graphics card. Obviously on a laptop there is no
choice when it comes to trying an alternative graphics card! I have also
tried the 2.6.24-18-xen kernel, but this doesn't seem to make any
difference. In a last-dit
Public bug reported:
Binary package hint: virt-manager
virt-manager doesn't appear to be able to create a Xen domU. When you
run the wizard to create a new VM on a Xen server, you are unable to
select a disk that exists or create a new image. In fact, no error
appears, the interface simply doesn'
I think this is a feature. If you launch virt-manager as root (sudo),
you are able to connect. Here is an extract from the libvirt site:
== >8 ==
Legacy: Xen proxy
Libvirt continues to support connections to a separately running Xen proxy
daemon.
This provides a way to allow
I suspect putting sleep in ~mythtv/.mythtv/session didnt work because its
executed in the background...(/usr/share/mythtv/startmythtv.sh)
echo "Checking for custom mythtv commands in ~/.mythtv/session"
if [ -x $HOME/.mythtv/session ]; then
$HOME/.mythtv/session &
fi
I have now edited startmyt
Has the fix mentioned here found its way into hardy yet?
https://bugs.launchpad.net/mythbuntu/+bug/139770
--
mythtv-frontend doesnt disable gnome-screensaver
https://bugs.launchpad.net/bugs/183990
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contac
On 23/01/2008, Mario Limonciello <[EMAIL PROTECTED]> wrote:
>
> The important part is the order in which the two are started. make sure
> that gnome screensaver is indeed fully started before myth is starting.
> You can try to experiment with adding a sleep in the ubuntu-mythtv-
> frontend session
same problem here...
--
package libmono-addins-gui0.2-cil 0.3-2 failed to install/upgrade: dependency
problems - leaving unconfigured
https://bugs.launchpad.net/bugs/184055
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
I think this is a duplicate of this bug:
https://bugs.launchpad.net/mythbuntu/+bug/139770
Apparently a fix was released on the 10/01/2008. My guess is that this
package hasn't filtered through yet.
--
mythtv-frontend doesnt disable gnome-screensaver
https://bugs.launchpad.net/bugs/183990
You re
Public bug reported:
I'm running hardy (18/01/2008) and have installed ubuntu-mythtv-frontend
(the package that causes the mythtv user to automatically login and
launch mythtv-frontend. The problem that I am seeing is that gnome-
screensaver seems to be kicking in after about 5 minutes and the scr
On 21/12/2007, Marcelo Boveto Shima <[EMAIL PROTECTED]> wrote:
>
> Included with some changes. There were some places that were using
> /var/run/$NAME.pid
> We have to take a closer look because I think the pidfile is created by
> the
> daemon itself not by start-stop-daemon.
Yes. I have played w
** Attachment added: "libvirt-bin_init_piddir.patch"
http://launchpadlibrarian.net/11020308/libvirt-bin_init_piddir.patch
--
[needs-packaging] virt-manager
https://bugs.launchpad.net/bugs/116897
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug conta
On 21/12/2007, Marcelo Boveto Shima <[EMAIL PROTECTED]> wrote:
>
> Ok, this happened some time ago to me when libvirtd sigfaulted, but the
> bridge was
> up and didn't went down. brctl didn't help me so to remove this bridge the
> only way
> I found was to reboot.
>
> Try to debug it by:
> disablin
On 21/12/2007, Marcelo Boveto Shima <[EMAIL PROTECTED]> wrote:
>
> On Dec 21, 2007 8:38 AM, Paul McEnery <[EMAIL PROTECTED]> wrote:
>
> > I added the above mentioned repository a while ago, but recently there
> > have been a few virt-manager/libvirt updates. I t
I added the above mentioned repository a while ago, but recently there
have been a few virt-manager/libvirt updates. I think these may have
been some upstream packages. Anyway, these packages dont seem to work
too well as /var/run/libvirt doesnt exist. I have made the following
change to the init f
Not sure if this is of any help to anyone. I have built binutils with
the nostrip option and installed libc6-dbg. Attached is a full backtrace
of the core.
** Attachment added: "backtract.txt"
http://launchpadlibrarian.net/10984899/backtract.txt
--
as crashed with SIGSEGV in strlen()
https:/
** Visibility changed to: Public
--
as crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/177083
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
I came up against this issue while trying to install a Centos4 domU
today.
I painstakingly went through the list and updated it so that I could
install a Centos4 domU. It started to get a little messy as the list had
to have hal and dbus added. I just added hal, dbus and all of their
dependencies
I think I have solved this one now, but cant test till the weekend.
After further scrutiny of the difference between feisty and gutsy
initrd's, I now see that gutsy simply copies your /etc/mdadm/mdadm.conf
into the initramfs. Feisty appears to generate a correct
/etc/mdadm/mdadm.conf with UUID's in
I have also tried placing the mdadm binary from the feisty initrd into
the gutsy initrd. This didn't work either. I guess the problem exists
somewhere else in the initrd.
Does anyone think this could be a problem with the version of mdadm that
created the raid device? I.e. The feisty initrd is the
I tried extracting the contents of both the 2.6.20 and 2.6.22 kernels. I
copied the lib/modules/2.6.22-14-generic (gutsy) into the lib/modules
directory of the feisty initrd. This booted up no problem. This proves
that the kernel is NOT the issue here.
As I said before, I believe the problem to be
I have also tried booting up with the gutsy CD into `rescue mode' and
rebuilt the initrd with dpkg-reconfigure linux-image-2.6.22-14-generic.
Needless to say, this didnt help.
I am beginning to wonder if this has anything to do with the version of
mdadm in the initrd? From the look of debugging in
I have tried installing 2.6.22-14-386 in addition to 2.6.22-14-generic
(default). neither of these kernels will boot. Are you saying that the
2.6.22-13-386 kernel worked for you as opposed to the 2.6.22-13-generic?
Note: its now 14 and not 13...
I am still not so sure its got anything to do with t
Ok. I tried backing out initramfs-tools and recreated the initrd. This
didnt help. I was able to capture the debug output. I did this by
appending `debug' at the kernel command line in grub. The attached is
the output generated in /tmp/ of the initramfs.
** Attachment added: "Initramfs debug outpu
I can confirm this problem too after an upgrade from Feisty to Gutsy,
but I don't think that the problem is a missing module (see below). Here
is my configuration:
Single hard disk (/dev/sda) configured with two Linux RAID Auto partitions.
$ sudo fdisk -l:
=
Disk /dev/sda:
On 20/10/2007, Mike Rutz <[EMAIL PROTECTED]> wrote:
>
> Trying to generate a new initrd for the working feisty kernel produces
> the same result here. Raid isn't detected only the lvms outside the
> raid. Every Initramfs generated with feisty works.
Ok. So it looks like the problem may well be i
Agreed my patch is probably more of a bug than a benefit, but hopefully
we can come up with something that does the job effectively and
efficiently. Initially I got most of the contents from an example
jabberd init script I found on the web. dbus does something similar.
here is what it does:
if
** Attachment added: "Mythbackend init script patch"
http://launchpadlibrarian.net/7934436/mythbackend.init.patch
--
init script unable to "start" after backend crash
https://bugs.launchpad.net/bugs/118538
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Public bug reported:
The init script for mythbackend simply checks for the existence of the
pid file. if the pid file exists, it assumes that mythbackend is
running. This is not necessarily the case. If you have something like
monit running to automatically restart in the event of a mythbackend
cr
David Morris said on 2007-05-25:
>
> Out of interest what file system are you using to store your recordings, and
> how full is the location your saving to
I am running with a default storage location of /var/lib/mythtv. This
has its own LVM logical volume with ext3 fs. The usage is very low at
After updating to the latest v4l-dvb drivers from linuxtv.org, things
seem to be a lot more stable. Since I cant quite get a core file to be
generated, I decided to start the backend in a screen session inside
gdb. After 24 hours of running, it finally crashed and here is the
output:
-
[Thread
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/7603401/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/7603403/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/7603404/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: gaim
Not sure what happened, gaim just crashed while the screen saver was on.
When I got back to my laptop and moved the mouse, apport had popped up.
This should be a full report attached.
ProblemType: Crash
Architecture: i386
Date: Fri May 11 10:04:45 2
After further testing and elimination of cards, it seems like the
C-1500 card is the one that causes a problem when changing channels
(intermittently). The module used by this card is `budget_ci'. It does
not use any firmware. It would appear that the problem is with the
drivers of this card. In th
I have 2 x DVB-C cards:
TT C-2300 and a TT C-1500. Both of these cards use the dvb_ttpci module and the
dvb-ttpci-01.fw
firmware. From the logs, it looks like changing channels causes the problem. As
a test, I have just
decided to try and swap which card is the one being used by adjusting the
Another crash.
Still no core file. If anyone knows why I am unable to generate one, it would
be much appreciated? I have now
tried with apport started and stopped, but cant seem to get the system to
generate one. This crash happened
with apport stopped and manually su'd to the mythtv user before
I have now installed all of the debug symbols packages, and have restarted both
apport and mythbackend.
Since then, I have seen a crash and noted the following entry in
/var/log/apport.log:
-
apport (pid 22491) Thu May 10 12:15:31 2007: called for pid 22155, signal 6
apport (pid 22491) Thu M
78 matches
Mail list logo