*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
Thanks for reporting this bug.
>From your log files:
Preparing to replace debconf 1.5.20 (using .../debconf_1.5.22_all.deb) ...
xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)'
failed.
*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
Thanks for reporting this bug.
The log files show:
Preparing to replace debconf 1.5.20 (using .../debconf_1.5.21_all.deb) ...
xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)'
failed.
Ab
*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
Thanks for reporting this bug.
The log files show:
Preparando para substituir debconf 1.5.20 (usando .../debconf_1.5.21_all.deb)
...
xargs: xargs.c:443: main: Afirmação `bc_ctl.arg_max <= (131072-2048)'
fal
*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
This is a bug in xargs from package findutils, reported as bug 234345. I will
mark this bug as duplicate.
Thanks for reporting this.
** This bug has been marked a duplicate of bug 234345
xargs: xargs.c:44
+1
Created a dangling symlink (/var/www/index.html -> /home/ubuntu/fake,
cat: /var/www/index.html: No such file or directory) and tried to
upgrade from gutsy to hardy. The upgrade failed with -proposed disabled
and succeeded with -proposed enabled. Tested in kvm VM.
--
package apache2.2-common 2
/lib/udev/rules.d/85-lvm2.rules contains RUN+="watershed sh -c '/sbin/lvm
vgscan; /sbin/lvm vgchange -a y'" and
watershed needs /var/run.
Previously /var/run was created in the initramfs by
/usr/share/initramfs-tools/hooks/udev.
Now watershed is a separate package, so I added "mkdir -p ${DESTDIR
GDM will only update the symlink for specific combinations of sequence
number / old gdm version, so it knows the symlink was not updated by the
system administrator. In this case, you changed the symlink yourself, so
gdm is not supposed to update it.
** Changed in: xorg-server (Ubuntu)
Stat
Fixed in:
hal (0.5.12~rc1-0ubuntu6)
* Add 00git_fix_drm_acls.patch: Fix copy&paste error which assigned
the wrong access_control.file for /dev/drm/card* devices. It
previously copied "input.device", but should be
"linux.device_file". This brings back hardware GL renderin
Fabien, the error message in your X log "(EE) config/hal: couldn't
initialise context: (null) ((null))" looks similar to bug 264256. It
seems gdm may be started before hal for you as well. That would also
explain why a gdm restart works fine.
Can you please check the sequence numbers of the symlin
Public bug reported:
Binary package hint: module-init-tools
Upgrading module-init-tools 3.7~pre7-3 within a jaunty chroot on a hardy system
failed.
Running /var/lib/dpkg/info/module-init-tools.postinst configure with set +e
gives:
Running depmod for 2.6.28-8-generic...
WARNING: Couldn't open
I have tested with two accounts, one old and one newly created.
The old account works fine when I login with password. Also manually umounting
and mounting Private works fine. However, this account was apparently created
before this bug was fixed, so automatic login is hit by comment 60 and 61.
Successfully tested in a hardy pbuilder.
A. with only hardy and hardy-updates enabled in the pbuilder the update failed:
Setting up tdsodbc (0.82-3) ...
rmdir: failed to remove `/var/lib/odbc': No such file or directory
The upgrade is completed but there were errors during the ugprade process.
B
** Bug watch added: GNOME Bug Tracker #533152
http://bugzilla.gnome.org/show_bug.cgi?id=533152
** Also affects: gwget via
http://bugzilla.gnome.org/show_bug.cgi?id=533152
Importance: Unknown
Status: Unknown
--
unable to select options in recursive option window (all selected)
htt
** Changed in: gwget2 (Ubuntu)
Assignee: Albert Damen (albrt) => (unassigned)
--
[jaunty] Please update gwget to 1.0.1 version
https://bugs.launchpad.net/bugs/334164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Public bug reported:
Binary package hint: apport
I had a crash in cpufreq-selector. When I wanted to report this crash by
clicking on the crash icon, then selecting Report, apport itself crashed.
As apport also couldn't report the apport crash, I have unpacked the crash file
with apport-unpack
** Attachment added: "ApportLog.txt"
http://launchpadlibrarian.net/23451194/ApportLog.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/23451195/Dependencies.txt
--
apport-gtk crashed: UnboundLocalError: local variable 'replacements' referenced
before assignment
h
** Attachment added: "Date"
http://launchpadlibrarian.net/23451355/Date
** Attachment added: "ExecutablePath"
http://launchpadlibrarian.net/23451356/ExecutablePath
** Attachment added: "InterpreterPath"
http://launchpadlibrarian.net/23451357/InterpreterPath
** Attachment added: "Proble
Fixed upstream in Revision 11329:
* src/cpufreq-selector/cpufreq-selector-service.c: Make enum error
values array static. Fixes bug #573762.
--
cpufreq-selector crashed with SIGSEGV in dbus_g_method_return_error()
https://bugs.launchpad.net/bugs/331044
You received this bug notification
Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch.
Without this patch compiz works fine again on jaunty / nvidia-glx-180.
--
compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2
https://bugs.launchpad.net/bugs/326344
You received this bug notification because you
The problem seems to come from the watch option added in 60-persistent-
storage.rules.
1. Booting with break=premount drops me in busybox without problems. With
break=mount the disk activity already starts.
2. Booting with break=premount, then starting udevd and calling udevadm trigger
--action=
Attached are the requested info files.
Tweaking 60-persistent-storage.rules I found the disk activity only
occurs when a watch is added on a partition used for LVM.
Attached are the modified rules and the resulting watches
in /dev/.udev/watch.
** Attachment added: "dpkgl.txt"
http://launchpadl
Attached are the requested tar files. I used the modified
60-persistent-storage.rules from comment 49 to be able to boot.
Somehow this feels like I won the lottery today. Only a handful of
systems is affected, but yet, I have two of those
There is a difference though: my laptop (Intel ICH8 /
Debugging manually with dbgsym packages installed gives a stacktrace with all
symbols resolved.
#0 gpm_cell_array_update (cell_array=0x16d9380) at gpm-cell-array.c:288
#1 0x00411d30 in gpm_cell_percent_changed_cb (cell=, percent=85084016, cell_array=0x20)
In frame #0 length seems to ind
-1
The .so symlinks added to libopencryptoki0 are already, as expected, in
libopencryptoki-dev. Therefore libopencryptoki-dev cannot be installed
anymore:
dpkg: error processing
/var/cache/apt/archives/libopencryptoki-dev_2.2.5+dfsg-1ubuntu1.2_amd64.deb
(--unpack):
trying to overwrite `/usr/li
Public bug reported:
Please sync enthought-traits-ui 2.0.4-3 (universe) from Debian unstable
(main)
The Ubuntu changes can be dropped as Debian has implemented all changes
required for python-central 0.6.
The package builds and installs fine in an intrepid pbuilder.
Debian changelog since last
*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
** This bug has been marked a duplicate of bug 234345
xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed.
--
package debconf 1.5.20 failed to install/upgrade:
https://bugs.launc
*** This bug is a duplicate of bug 234345 ***
https://bugs.launchpad.net/bugs/234345
** This bug has been marked a duplicate of bug 234345
xargs: xargs.c:443: main: Assertion `bc_ctl.arg_max <= (131072-2048)' failed.
--
debconf failed to upgrade from hardy to intrepid
https://bugs.launchp
With 1ubuntu6 the -dev package can be installed again, but we are back
at the original issue. The .so symlink for libopencryptoki is not
available if the -dev is not installed:
Error loading PKCS#11 library
dlopen error: libopencryptoki.so: cannot open shared object file: No such file
or director
I was able to reproduce this on my 945 and got a full backtrace.
** Attachment added: "totem-crash.txt"
http://launchpadlibrarian.net/24835744/totem-crash.txt
--
crash in drm_intel_gem_bo_start_gtt_access
https://bugs.launchpad.net/bugs/354688
You received this bug notification because you ar
The problem is in xxv-intel, src/i830_video.c
In I830PutImage:
if (pPriv->buf == NULL) {
pPriv->buf = drm_intel_bo_alloc(pI830->bufmgr,
"xv buffer", alloc_size, 4096);
if (pPriv->buf == NULL)
return BadAlloc;
if (!pPriv
** Bug watch added: freedesktop.org Bugzilla #21060
https://bugs.freedesktop.org/show_bug.cgi?id=21060
** Also affects: xserver-xorg-video-intel via
https://bugs.freedesktop.org/show_bug.cgi?id=21060
Importance: Unknown
Status: Unknown
--
crash in drm_intel_gem_bo_start_gtt_acces
(EE) intel(0): Cannot support DRI with frame buffer width > 2048
caused by:
SubSection "Display"
Virtual 2640 800
EndSubSection
was the problem.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Fix Committed => Invalid
--
Compiz doesn't start after upgrade xorg-video-inte
Given you have a GM945 and Xorg.0.log contains the lines
(EE) intel(0): Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on depth buffer: rejected by kernel
you are most likely seein
Your Xorg.0.log shows you are using an intrepid kernel (Current Operating
System: Linux skynet 2.6.27-7-generic).
This kernel does not support GEM, therefore you cannot use UXA.
EXA with a non-gem kernel is slow due to bug
http://bugs.freedesktop.org/show_bug.cgi?id=20797 (Non-GEM allocations
in
Your xorg.conf contains the line:
Virtual 3200 1200
Therefore DRI cannot be used:
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
In Intrepid XV could still be used with overlay video. In jaunty XV
overlay needs DRI as well.
As a workaround you can use non-XV video, like you al
No problem Péter, thanks for confirming all is ok now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Triaged => Invalid
--
[G33] performance drop (20-40fps) in games and compiz after upgrade to Jaunty
https://bugs.launchpad.net/bugs/359629
You received this bug notification bec
This is fixed in Debian, libpcap 1.0.0-1:
* debian/patches/20-fix-any-intf.diff: New patch cherry-picked from
upstream; fixes handling of the 'any' device.
The any interface can be used in both tcpdump and wireshark again.
$ sudo tcpdump -D
1.eth0
2.wmaster0
3.wlan0
4.any (Pseudo-device th
** Description changed:
+ Please sync libpcap 1.0.0-1 (main) from Debian unstable (main)
+
+ Motivation: the update fixes a bug where the any pseudo interface cannot
+ be used in tcpdump.
+
+ The package builds fine in a jaunty pbuilder and installs and runs fine on a
jaunty system. Tested with
This bug is fixed in gnome-power-manager svn revision 2882:
* src/gpm-cell-array.c: (gpm_cell_percent_changed_cb):
The callback passes a gfloat, not a guint.
I applied the patch and gpm does not crash anymore.
** Bug watch added: GNOME Bug Tracker #547766
http://bugzilla.gnome.org/show_bug.cg
Confirmed.
atlas fails to build from source on i386. See
http://launchpadlibrarian.net/16970147/buildlog_ubuntu-intrepid-i386.atlas_3.6.0-21.5ubuntu1_FAILEDTOBUILD.txt.gz.
Therefore you get the old 3.6.0-21.1ubuntu3 libatlas-base-dev version, which
does not depend on libgfortran3.
On amd64 atla
Thanks for reporting this bug. Pyparsing 1.5.0 has been uploaded to
Intrepid (the development version of Ubuntu), so I will close this
request.
python-pyparsing |1.5.0-1 | intrepid/universe | all
** Changed in: pyparsing (Ubuntu)
Status: New => Fix Released
--
new upstream version av
This was fixed in pygobject:
pygobject (2.15.3-0ubuntu3)
* New patch, 69_pyg-register-pointer-typo, fixes crash on x86-64 due to
typo (s/&type/type) in pyg_register_pointer(); GNOME #550463.
* Remove the bogus Breaks added in 2.15.3-0ubuntu2.
and indeed also python-gtk2 2.13 was
** Summary changed:
- Atlas blas and lapack libraries unware of gfortran dependency
+ Please merge atlas 3.6.0-22 (universe) from Debian unstable (main)
** Changed in: atlas (Ubuntu)
Assignee: (unassigned) => Albert Damen (albrt)
Status: Confirmed => In Progress
** Bug watch
Please sponsor the attached debdiff.
The merged package builds fine in an i386 pbuilder on i386.
Please note, it will not build in an i386 pbuilder on amd64, as atlas uses
uname to detect the architecture, which detects the host arch instead of the
chroot arch.
The required files can be found on
Attached is the debdiff between the old and new ubuntu versions.
** Attachment added: "ubuntu-ubuntu.debdiff"
http://launchpadlibrarian.net/17348094/ubuntu-ubuntu.debdiff
** Changed in: atlas (Ubuntu)
Assignee: Albert Damen (albrt) => (unassigned)
Status: In Progress
Those lines in xsession-errors confirm compiz sets LIBGL_ALWAYS_INDIRECT:
Checking for texture_from_pixmap: not present.
Trying again with indirect rendering:
Checking for texture_from_pixmap: present.
However, your X log shows texture_from_pixmap is supported by the driver:
(II) AIGLX: enabled
ACL handling has moved again, now from udev-extras into udev (in 143-1).
As xserver-xorg already recommends udev, this issue should be fixed now.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Fix Released
--
[i945gme] Xorg very slow after upgrade
https://bugs.launc
Hi George,
to debug this issue, we need a bit more information:
- please attach the file .xsession-errors (from your home directory)
- please run the command glxinfo > glxinfo.txt and attach the file glxinfo.txt
Most likely LIBGL_ALWAYS_INDIRECT is set by compiz. Can you disable compiz and
let u
In Karmic you are using KMS. With KMS the names of the outputs have changed.
VGA is now VGA1 and LVDS is now LVDS1.
These are the output names you have to use in xrandr commands.
So, most likely, xrandr --output VGA1 --right-of LVDS1 --auto will do something
now.
Please let us know if that solves
** Visibility changed to: Public
--
nautilus crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/413660
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
https://lists.
Attached is the output of hal-device
/org/freedesktop/Hal/devices/storage_model_DVDRW_SSM_8515S
There was no disk in the drive.
The crash happened before I could start anything myself.
** Attachment added: "haldevice.txt"
http://launchpadlibrarian.net/30322126/haldevice.txt
--
nautilus crash
Upstream git commit c255543c "Should fix #591826 – nautilus crashed with
SIGSEGV in strcmp()" solves the problem for me.
--
nautilus crashed with SIGSEGV in strcmp()
https://bugs.launchpad.net/bugs/413660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
You are using the server kernel, which uses PAE. GEM is not compatible with PAE
and is therefore disabled.
That means you get the fake bufmgr, which is too small to handle video
correctly (fake bufmgr (1024 kB)).
Unfortunately, allocating more memory for the fake bufmgr was tried during
jaunty d
*** This bug is a duplicate of bug 363821 ***
https://bugs.launchpad.net/bugs/363821
Blacklisted PCIID '8086:2a02' found
Compiz was disabled for GM965 in jaunty because of a major freeze bug. This is
not related to UXA.
See bug 363821 for the current status and suggestion how you can enable
You are using the intrepid kernel (2.6.27-11-generic x86_64), which does not
have GEM.
To play video in jaunty, you do need to use a gem enabled kernel.
Can you please test with the jaunty kernel (2.6.28-11-generic) and let us know
if that works?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Current Operating System: Linux mpt-ubuntu 2.6.27-11-generic #1 SMP Wed
Apr 1 20:57:48 UTC 2009 i686
You are using the Intrepid kernel, which does not have GEM. The fake bufmgr
which you get instead of GEM is too small to play video. If you want to play
video, you will need to use the jaunty ker
ProcVersion: Linux version 2.6.24-19-server
You are using a hardy server kernel, which does not have GEM.
Can you please install the jaunty generic kernel (2.6.28-11-generic) and boot
and test with that kernel?
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Confirmed => Incomple
I just run into the same problem. The wireshark-root desktop file has
the line: TryExec=su-to-root. However, the su-to-root program did not
exist on my system. It is provided by the "menu" package, and installing
this package made the wireshark (as root) option appear.
--
no run as root in menu i
Bug and patch forwarded to Debian.
** Bug watch added: Debian Bug tracker #476527
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476527
** Also affects: mnemosyne (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476527
Importance: Unknown
Status: Unknown
--
mnemos
** Changed in: opendict (Ubuntu)
Assignee: (unassigned) => Albert Damen (albrt)
Status: New => In Progress
--
missing dependency python-xml in opendict package (Ubuntu Hardy Beta)
https://bugs.launchpad.net/bugs/208140
You received this bug notification because you are a mem
rarian.net/13576525/opendict.debdiff
** Changed in: opendict (Ubuntu)
Assignee: Albert Damen (albrt) => (unassigned)
Status: In Progress => New
--
missing dependency python-xml in opendict package (Ubuntu Hardy Beta)
https://bugs.launchpad.net/bugs/208140
You received this
** Summary changed:
- link-monitor-applet dependency problems
+ Please sync link-monitor-applet 3.0-1 (universe) from Debian unstable
** Description changed:
+ Please sync link-monitor-applet 3.0-1 (universe) from Debian unstable
+
+ Current version of link-monitor-applet in Hardy, 2.1-2, brea
** Attachment added: "diffstat.txt"
http://launchpadlibrarian.net/13581755/diffstat.txt
--
Please sync link-monitor-applet 3.0-1 (universe) from Debian unstable
https://bugs.launchpad.net/bugs/185318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Attachment added: "buildlog.txt"
http://launchpadlibrarian.net/13581763/buildlog.txt
** Changed in: link-monitor-applet (Ubuntu)
Status: Confirmed => New
--
Please sync link-monitor-applet 3.0-1 (universe) from Debian unstable
https://bugs.launchpad.net/bugs/185318
You received thi
Could somebody please sponsor this sync request?
--
Please sync link-monitor-applet 3.0-1 (universe) from Debian unstable
https://bugs.launchpad.net/bugs/185318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This is documented in /usr/share/doc/python-matplotlib/INTERACTIVE :
To use matplotlib interactively from the prompt, you need a special
interpreter that doesn't enter the gtk mainloop. One is provided in
examples/interactive.py. The coew functionality of this interpreter
was provided by Brian M
*** This bug is a duplicate of bug 213863 ***
https://bugs.launchpad.net/bugs/213863
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 213874, so it is being marked as such. Please look at
Please find attached an updated debdiff.
I did not fix below lintian error and warnings:
W: kerry: binary-without-manpage usr/bin/beagled-shutdown
- correct, there is no man page
E: kerry: no-shlibs-control-file usr/lib/libkdeinit_kerry.so
- this is due to missing soname version; a soname version
Err, I did not change the maintainer field, as the maintainer already
has an ubuntu.com address and the spec says not to change that.
** Changed in: kerry (Ubuntu)
Assignee: Albert Damen (albrt) => (unassigned)
Status: In Progress => Confirmed
--
[hardy] kerry does not i
** Changed in: mnemosyne (Ubuntu)
Assignee: (unassigned) => Albert Damen (albrt)
Status: New => In Progress
--
mnemosyne crashed with AttributeError in ()
https://bugs.launchpad.net/bugs/206958
You received this bug notification because you are a member of Ubuntu
Bugs, wh
rarian.net/13287965/mnemosyne.debdiff
** Changed in: mnemosyne (Ubuntu)
Assignee: Albert Damen (albrt) => (unassigned)
Status: In Progress => Confirmed
--
mnemosyne crashed with AttributeError in ()
https://bugs.launchpad.net/bugs/206958
You received this bug notification because you
Yes I can. However, feel free to close this bug as I seem to be the only
one who notices this and I can live with it.
--
should not be able to resize past viewport
https://bugs.launchpad.net/bugs/137134
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
>> where Mnemosyne was installed from its website.
That is exactly the problem. The installation from the mnemosyne website
puts the files in a different directory then the Ubuntu package and
these files cannot be replaced by the Ubuntu mnemosyne package. You will
need to remove the mnemosyne file
ACK
- verified rkward 0.4.9-2 fails to start on amd64
- upgraded to 0.4.9-2ubuntu0.1 successfully
- rkward 0.4.9-2ubuntu0.1 runs fine on amd64
--
Not working in hardy x64
https://bugs.launchpad.net/bugs/221399
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 222876 ***
https://bugs.launchpad.net/bugs/222876
Thanks for your bug report. This problem is already known as bug 222876.
Work is in progress to solve it.
** This bug has been marked a duplicate of bug 222876
package gcc-3.3-doc 1:3.3.6-15ubuntu4 failed
*** This bug is a duplicate of bug 205348 ***
https://bugs.launchpad.net/bugs/205348
Thanks for your bug report. This problem has already been reported in
bug 205348 and work is in progress to solve it.
** This bug has been marked a duplicate of bug 205348
gcc-3.4-doc uphgrade failed due t
Apparently the retracer for Hardy does not work anymore.
** Changed in: serpentine (Ubuntu)
Status: New => Invalid
--
serpentine crashed with SIGSEGV in g_type_check_instance()
https://bugs.launchpad.net/bugs/226452
You received this bug notification because you are a member of Ubuntu
Bug
Public bug reported:
Binary package hint: serpentine
Trying to debug the frequent crash reports on serpentine on upgrades
from Gutsy to Hardy, I did an upgrade test with a Gutsy VM (amd64, no
cdrom attached) in KVM.
- Start Gutsy VM
- Verify serpentine is installed
- Upgrade to Hardy
- Reboot th
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/14194491/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/14194492/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/14194493/Disassembly.txt
** Attachm
efault pager command. (Closes: #266365).
+ Thanks to Albert Damen.
* Fix German translations. (Closes: #313710).
+ Thanks to Jens Seidel for the patch.
* All Saints Day on some states. (Close: #396378).
+ Thanks to Marc-Jano Knopp for the patch.
* Fix typo in copyright and upda
SRU test failed
Trying to install gcc-3.4-doc in a hardy pbuilder with hardy-proposed
enabled fails with the following error message:
Unpacking gcc-3.4-base (from .../gcc-3.4-base_3.4.6-6ubuntu4_amd64.deb) ...
Selecting previously deselected package gcc-3.4-doc.
Unpacking gcc-3.4-doc (from .../gc
Thanks for reporting this bug.
Can you please attach the files from /var/log/dist-upgrade/ to this bug report?
Those files are the logs of the upgrade and will give us more information about
what went wrong.
** Changed in: gcl (Ubuntu)
Status: New => Incomplete
--
gcl failed to upgrade
The Traceback shows the crash happens in the file
/usr/lib/python2.5/site-packages/mnemosyne/core/mnemosyne_core.py
This file is not used by the Ubuntu package. The Ubuntu package would install
that file as
/usr/share/python-support/mnemosyne/mnemosyne/core/mnemosyne_core.py and create
a symlin
Glad to hear it is working now. I will close this bug report.
** Changed in: mnemosyne (Ubuntu)
Status: Incomplete => Invalid
--
mnemosyne crashed with AttributeError in () - still broken
https://bugs.launchpad.net/bugs/221438
You received this bug notification because you are a member of
This has been fixed in Hardy, where we now have link-monitor-applet
3.0-1.
** Changed in: link-monitor-applet (Ubuntu)
Status: Confirmed => Fix Released
--
Close button doesn't work on About dialog
https://bugs.launchpad.net/bugs/157327
You received this bug notification because you are a
This has been fixed in link-monitor-applet 3.0-1, which we now have in
Hardy.
** Changed in: link-monitor-applet (Ubuntu)
Status: Confirmed => Fix Released
--
link-monitor-applet crash on new host
https://bugs.launchpad.net/bugs/157326
You received this bug notification because you are a
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
- Can you please run the command: apt-cache policy sysv-rc end paste the
results in this bug report?
- Please also attach the file /etc/apt/sources.list as attachment.
This will he
That symbol is supposed to come from libeel2-2:
[EMAIL PROTECTED]:~$ nm -D /usr/lib/libeel-2.so.2 | grep drect_empty
00053500 R eel_drect_empty
- Can you please run the command "apt-cache policy libeel2-2" and paste the
results in this bug report?
- Please also run the command "apt-cache policy
This problem is caused by the version of sysv-rc you have installed. That is a
version from Debian. In Ubuntu Hardy you should have sysv-rc version
2.86.ds1-14.1ubuntu45. Unfortunately, the Debian version does not know the
multiuser option to update-rc.d which is used in Ubuntu.
To solve the pro
Thanks for reporting this bug. I can reproduce it in a Hardy pbuilder:
Unpacking gcc-3.3-base (from .../gcc-3.3-base_1%3a3.3.6-15ubuntu4_amd64.deb) ...
Selecting previously deselected package gcc-3.3-doc.
Unpacking gcc-3.3-doc (from .../gcc-3.3-doc_1%3a3.3.6-15ubuntu4_all.deb) ...
Setting up gcc-3
*** This bug is a duplicate of bug 222876 ***
https://bugs.launchpad.net/bugs/222876
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 222876, so it is being marked as such. Please look at
** Changed in: mnemosyne (Ubuntu)
Status: Confirmed => New
--
mnemosyne crashed with AttributeError in ()
https://bugs.launchpad.net/bugs/206958
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
+1
hardy-proposed/universe gcc-3.4-doc 3.4.6-6ubuntu5 installed without problems
in a hardy pbuilder.
info gcc, info gccint and info gccinstall produce useful output.
--
gcc-3.4-doc uphgrade failed due to missing usr/share/info/gcc-3.4.info.gz
https://bugs.launchpad.net/bugs/205348
You received
+1
hardy-proposed/universe gcc-3.3-doc 1:3.3.6-15ubuntu6 installed without
problems in a hardy pbuilder.
info gcc and info gccint give useful output.
--
package gcc-3.3-doc 1:3.3.6-15ubuntu4 failed to install/upgrade:
https://bugs.launchpad.net/bugs/222876
You received this bug notification bec
*** This bug is a duplicate of bug 227878 ***
https://bugs.launchpad.net/bugs/227878
Thanks for reporting this bug. The same bug is reported in bug 227878,
so I will mark this bug as a duplicate.
** This bug has been marked a duplicate of bug 227878
gcl failed to upgrade from Ubuntu 7.10 t
*** This bug is a duplicate of bug 227878 ***
https://bugs.launchpad.net/bugs/227878
We have got log files in bug 227878, so I mark this a s a duplicate.
** This bug has been marked a duplicate of bug 227878
gcl failed to upgrade from Ubuntu 7.10 to 8.04.
--
package gcl 2.6.7-34 failed t
Thanks cremlae, these log files really help.
>From the logs:
Selecting previously deselected package emacsen-common.
Unpacking emacsen-common (from .../emacsen-common_1.4.17_all.deb) ...
Preparing to replace gcl 2.6.7-34 (using .../archives/gcl_2.6.7-36_i386.deb) ...
ERROR: emacsen-common being
I hope I am not impatient, but I believe this bug is not ready for verification
yet.
Testing the upgrade from Gutsy to Hardy with axyl-lucene installed and
hardy-proposed enabled still fails:
dpkg - trying script from the new package instead ...
/usr/share/axyl/install/axyl-common-funcs.sh: 185:
This is a slightly different bug then bug 161226, as nagios2 is now terminated
when nagios2 reload is called.
It is again due to a bug in lsb-base. Below lines are the cause of the problem.
Any signal passed to killproc (from /lib/lsb/init-functions) is treated as
SIGTERM.
This bug in lsb-base
The lines from killproc:
killproc () {
[...]
sig=$(echo ${2:-} | sed -e 's/^-\(.*\)/\1/')
sig=$(echo $sig | sed -e 's/^SIG\(.*\)/\1/')
if [ -n "$sig" -o "$sig" = 15 -o "$sig" = TERM ]; then
is_term_sig=yes
fi
--
/etc/init.d/nagios2 reload kills nagios
https://bugs.lau
101 - 200 of 335 matches
Mail list logo
