Public bug reported:
Currently attempts to use libfdt-dev will fail as the packaging doesn't
include the libfdt_env.h header required by the others. One place this
breaks for example is trying to compile the current QEMU using system
libraries. This has already been fixed upstream so the fix
This is the upstream bug-report: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=706137
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218819
Title:
libfdt-dev is broken for current LTS release
I can confirm that after hand-building Debian's device-tree-
compiler_1.3.0-4 packages and installing them I could successfully build
something using libfdt-dev (qemu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I have verified that the proposed dpkg no longer hangs. I used the
following script to generate heavy load on the system:
#!/bin/bash
#
# Generate IO load
echo starting load
#dd if=/dev/zero of=zero
sleep 1s
dd if=/dev/urandom of=urandom
sleep 1s
dd if=/dev/sda1 of=sda1_backup1
sleep 1s
dd
Thanks to Ted for clearly elucidating the two competing issues. For the
time being we can't move from 10.04 (whole OS upgrades tend to be
unpopular with customers for point releases). However as the kernel lock
is always triggered by dpkg I'm hoping that just fixing dpkg will be
enough. I assume
Surely the fix required is for the kernel? While dpkg might be good at
triggering the bug it may not be the only thing that can hang the kernel
requiring a hard reset.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The behaviour we are seeing is dpkg hangs and never returns. As dpkg is
left in the D state and is un-killable the only recourse is to hard
reset the box (power-cycle) it. However it might be due to file-system
load it can never achieve the file-system sync. I'm currently trying to
come up with a
I'm confused as to when this fix was released. I can't see any
reference to this bug in the changelogs of either dpkg or the linux-
image. I'm seeing on customer 10.04LTS machines running the latest
packages which makes me think the bug is still there.
--
You received this bug notification
I suspect the invoke-rc.d line needs to be wrapped in the -e part of the
of the check?
The current preinst code looks like:
# Manually remove the nis init script, which has to be split into per-daemon
# upstart jobs
if dpkg --compare-versions $2 lt-nl 3.17-32ubuntu1.1
then
# since this
Public bug reported:
On upgrading to Precise I find that apt cannot complete due to a
--unpack failure running the pre-installation script.
dpkg --unpack /var/cache/apt/archives/nis_3.17-32ubuntu4_amd64.deb
(Reading database ... 313937 files and directories currently installed.)
Preparing to
I suspect the invoke-rc.d line needs to be wrapped in the -e part of the
of the check?
The current preinst code looks like:
# Manually remove the nis init script, which has to be split into per-daemon
# upstart jobs
if dpkg --compare-versions $2 lt-nl 3.17-32ubuntu1.1
then
# since this
Following a weekend of my work machine idling and doing nothing I can
now report gnome-keyring-daemon is taking up 8.7% of my memory:
983M (VIRT) 677M (RES) 8.7% MEM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apologies - this package is part of the Gnome 3 PPA. According to
#179873 I can't assign this bug to a PPA so I'm unsure what to do. Will
contact the PPA manager directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There seems to be a persistent leak in gnome-keyring-daemon. Several
times I've come into work to find a very sluggish machine swapping
applications back in with the daemon consuming 45% of my system memory
(according to htop on an 8GB machine). If there is any debugging tips
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/930330/+attachment/2730042/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930330
Does that make this an upstream bug for Debian?
I've also found another package without debug symbols (libgdk-
pixbuf2.0-0), should I raise a bug for that as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 5 January 2012 16:52, Kurt Roeckx k...@roeckx.be wrote:
On Tue, Dec 20, 2011 at 05:33:51PM +, Alex Bennee wrote:
On 20 December 2011 15:46, Tobias Oetiker t...@oetiker.ch wrote:
Hi Alex,
Yesterday Alex Bennee wrote:
On 19 December 2011 17:00, Tobias Oetiker t...@oetiker.ch wrote
Public bug reported:
I'm trying to do some system profiling on a server that's behaving
poorly while cloning repositories. To do proper profiling I need the
debug symbols but I can find them even with the ddebs.ubuntu.com repo
added.
root@vsbldhost:/scratch/root# apt-cache search dbg | grep git
Public bug reported:
Unfortunately I need Moonlight installed to use an internal intranet
site. After following link on the 'net I found a suggestion it should be
apt-get 'able. However according to the package page:
http://packages.ubuntu.com/source/natty/moon there is no version built
for
I can confirm this happens. A strace very clearly shows it ignoring me:
29077 execve(/usr/bin/debmirror, [debmirror, --host, sloy,
--method=http, -r, apt, --dist=repo, --arch=amd64,source,
--section=main, VNMS_2.1.32-0], [/* 83 vars */]) = 0
29078 execve(/bin/sh, [sh, -c, patch --version
This looks like it's an upstream change. From the man-page:
--rsync-extra=foo[,bar,..]
Allows to also mirror files from a number of directories that are
not part of the package archive itself.
Debmirror will always use rsync for the transfer of these files,
irrespective
The core dump is because of the assertion failure. Somehow the
processing of /proc/timer_stats has broken. I can't see anything obvious
as to why. I'd suggest running it under valgrind and seeing if that
throws up any warnings.
I have seen some other interesting core dumps on 10.04 in various
I tried the steps described in #157 (although I couldn't find the
Gwibber permissions/authorization on FAcebook's site, I just deleted to
the App). When attempting to login via the Gwibber status panel I get
success reported in the text box but no Add button.
I'm running the Gwibber PPA on 10.04
Public bug reported:
Shortly after inserting a USB key into my hub the kernel oopsed on
accessing my other removable USB drive which I keep permanently
connected to my machine. It looks as though the addition of the key may
have caused by previously mounted drive to be re-registered on a new
I can't test the current setup on Lucid, we are using LTS for a reason.
I can test when transition to the next LTS release. However from your
experiments it sounds like a problem that only affects the LTS and has
been fixed from updates to the build system.
--
Unable to create valid debug
Will there ever be a release for Hardy LTS?
--
No debug symbols package for net-snmp
https://bugs.launchpad.net/bugs/273099
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in ubuntu.
--
Ubuntu-server-bugs mailing list
Will there ever be a release for Hardy LTS?
--
No debug symbols package for net-snmp
https://bugs.launchpad.net/bugs/273099
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
What package update is meant to have fixed this. I have the same problem
that the Unlock button is greyed out for most of the admin tools when
I access the server with ssh -Y and vncviewer. The suggested work
around (#26) doesn't seem to have any effect.
Obviously it's a bit crippling not being
I wrote a quick script and found that the only debug symbols I'm sure
are suspect were the origin -dbg version of the libcairo ones. There are
a bunch of files in the top level of /usr/lib/debug which don't match
but I was kinda guessing, e.g.:
14:31 a...@pitcairn/x86_64 [dbgsym.git] ./dbgsym.py
The problem is that when the library was built the CRC of the debug
symbols file gets planted in the main library file. OProfile very
sensibly checks that the CRC of the debug file matches that stored in
the actual library and ignores it if it doesn't.
GDB may well work and having hacked oprofile
It could be this only affects the Hardy packages? Or maybe something
more subtle?
As you say GDB should complain but it certainly doesn't seem fussy:
v...@vnms:~$ gdb /usr/bin/gnome-terminal
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
Just for completeness are there any pointers to using the pkg-create-
dbgsym package? Installing it and rebuilding the package doesn't seem
to have worked.
--
libcairo2-dbg CRC doesn't match symbol (I suspect this is more widespread)
https://bugs.launchpad.net/bugs/415424
You received this bug
It looks like this is a bug in the tools. I installed pkg-create-
dbgsym and rebuilt cairo from scratch and installed the new packages
and I still get failures due to bad CRCs. I shall raise a new bug as I
doubt this is the libcairo package explicitly.
--
libcairo2-dbg CRC doesn't match symbol
Public bug reported:
Following on from my investigation into LP#415424 it seems even the
correct way of installing pkg-create-dbgsym doesn't allow the
generation of correct debug packages.
Although the packages are usable by the likes of GDB tools like oprofile
rightly complain when they
Hmm I thought Launchpad would ask me, however I'm running Hardy LTS.
--
Unable to create valid debug packages from some packages
https://bugs.launchpad.net/bugs/423748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Is this a disk that has worked before? I'm completely guessing as I
don't have lsdvd on any Ubuntu systems, but on other systems I've seen
crashes with interesting discs. I'd done a hacky patch to it to make it
slightly more robust:
commit aadfb3181c94b6e1ee1708fd256df5654e5533a4
Author: Alex
I was rebuilding from source after install the pkg-create-dbgsyms
package. Although curiously installing a dbgsym from the repo you
referenced:
apt-get install libcairo2-dbgsym
followed by opreport:
snip
fetching .gnu_debuglink section
.gnu_debuglink section has size 18
.gnu_debuglink filename
Two cases:
1. Built from source (with pkg-create-dbgsyms installed). Installed my
locally built package with the locally built dbgsym ddeb:
sudo dpkg -i libcairo2-dbgsym_1.6.0-0ubuntu2_amd64.ddeb
libcairo2_1.6.0-0ubuntu2_amd64.deb
The CRCs didn't match leading me to raise #423748.
2. Installed
Public bug reported:
While attempting to oprofile something on my Hardy system I discovered
the following:
v...@vnms1:~/ajb$ opreport -V bfd -l /usr/lib/libcairo.so.2.17.3
CPU: Core 2, speed 2500 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask
of
Can confirm this is still a problem on 8.04 Hardy Heron. I guess bugs
don't get fixed on Hardy unless they are confirmed on later builds :-(
--
detect lan printers no longer settable
https://bugs.launchpad.net/bugs/219907
You received this bug notification because you are a member of Ubuntu
Sorry for the delay. Unfortunately I can't just upgrade my development
machine at work just to test the new X drivers. We are developing
against LTS for a reason. I've added the lspci output for reference if
it ever gets looked at again.
** Attachment added: lscpi -vvnn output
Just to echo eNz1m3 as I've just run into this very same bug. Does Hardy
not get updates for bugs like this. It is meant to be a LTS system and
this is a breaking the desktop bug.
--
Clock applet doesn't load when Google Calendar is used in Evolution
https://bugs.launchpad.net/bugs/194505
You
Public bug reported:
Running valgrind against some programs built with libsnmp I came across
some invalid reads. Unfortunately it's in the guts of net-snmp and there
is no debug symbol package to install to help elucidate whats going on.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Public bug reported:
Running valgrind against some programs built with libsnmp I came across
some invalid reads. Unfortunately it's in the guts of net-snmp and there
is no debug symbol package to install to help elucidate whats going on.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
Since todays updates it's started crashing for me on BBC's iplayer
website. Seems flash-like
--
gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/252174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hmm is there anyway to get the auto bug report daemon to append
additional information to existing bugs?
--
xfce4-places-plugin crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/259858
You received this bug notification because you are a member of Ubuntu
Bugs,
My current work-around was to build an image with ubuntu-kvm-image-
builder, boot it with the server CDROM (for some reason despite having a
working GRUB it failed to install a kernel image), install the image and
the reboot.
--
ubuntu-server install fails at grub-install stage when running in a
** Attachment added: grub-fail.png
http://launchpadlibrarian.net/16379302/grub-fail.png
--
ubuntu-server install fails at grub-install stage when running in a KVM image
https://bugs.launchpad.net/bugs/252901
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: grub-installer
When installing the latest Ubuntu Server into a KVM machine the install
locks up at the point it tries to install the grub bootloader. Further
investigation shows it fails after installing stage_1_5. It will hag
after that point although
Public bug reported:
Binary package hint: hal-info
Usually this works once and then fails on future insertions.
Occasionally the device will mount if the machine is under heavy load
which may indicate some sort of race.
Looking at gnome-volume-manager it's fairly clear why it doesn't
proceed:
I have to echo Dave Millers comments. There have been a lot of kernel
updates recently and it seems rather Windowsy to force everyone to
reboot just for some boot time saving. In future it might be worth
keeping fixes like this rolled up until the next security/bug fix
before pushing out to
Public bug reported:
Binary package hint: nvidia-kernel-common
When exiting the screen saver my X session crashed leaving the screen
corrupted. It was possible to ssh into the box although the screen saver
processes where using most of the CPU time. I was unable to restart X
with the
** Attachment added: lscpi output for system
http://launchpadlibrarian.net/14343414/lspci.dump
** Also affects: linux-restricted-modules-2.6.24 (Ubuntu)
Importance: Undecided
Status: New
--
MirrorBlob screen saver crashes X hard with nvidia drivers
** Attachment added: kernel log showing hang in kernel and crash
http://launchpadlibrarian.net/14343431/kern.subset.log
--
MirrorBlob screen saver crashes X hard with nvidia drivers
https://bugs.launchpad.net/bugs/227849
You received this bug notification because you are a member of Ubuntu
I'm not sure if this is related or not. On my setup:
15:19 [EMAIL PROTECTED]/x86_64 [Desktop] cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION=Ubuntu 7.10
15:21 [EMAIL PROTECTED]/x86_64 [Desktop] dpkg -l mplayer
ii mplayer
The pci-id I have here is also 01:00.0 0300: 1002:94c1
I see someone else has already tested the Hardy package. However the
particulars of the driver that envy installed are:
(somewhat trimmed)
Envy - Version 0.9.10
Ubuntu Gutsy 64bit
Your graphic card has been detected as a ATI RADEON HD 2400
Public bug reported:
Binary package hint: restricted-manager
I did a fresh install on 7.10 (Gutsy) on a fresh Dell Optiplex 755. The
machine has an ATI chipset which is unidentified by it's PCI ID:
01:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 94c1
(prog-if 00 [VGA
Public bug reported:
Binary package hint: linux-ps3
After installing the Fiesty Custom image the Wireless network of the PS3
is not detected. This may be related to the recent update of the GameOS
Firmware to 2.0.
The kernel version was:
2.6.20-15-powerpc64-smp #3 Apr
(For Reference: YDL have
Public bug reported:
Binary package hint: udev
Whilst trying to get more info on bug 115616 I would like to look at
where in udev the ioctl is coming from. However the udev package is
currently missing a debuginfo package.
** Affects: udev (Ubuntu)
Importance: Undecided
Status:
I've seeing the same thing but with a command line openvpn connection.
However the patch to the script didn't seem to work. In my case the
initial connection is being handled by wpa_supplicant and uses dhclient
not dhclient3
--
resolv.conf overwritten using VPN/PPP etc...
The ubuntu driver showed up as 0.14.3 and upstream 0.14.4 had a bunch of
fixes for 64 bit issues.
I was having the same problem with random pastes caused by phantom 3rd
button presses each time I put my finger on the touchpad (even if I had
disabled tapping). I have since manually updated to the
61 matches
Mail list logo
