The bug is fixed in dbab 1.2.2-1 which is now in vivid.
** Changed in: dbab (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406993
Title:
Missing "d
The bug is already fixed in upstream git:
https://github.com/suntong001/dbab/commit/f1198980df9a45459b424174bc420c22caa487d7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1406993
Title:
Missing "dba
** No longer affects: hundredpapercuts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400662
Title:
[vivid] upstart: gnome-keyring-gpg main process (1504) terminated with
status 2
To manage notif
** Patch added: "gnome-keyring_3.14.0-1ubuntu1+sero1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1400662/+attachment/4287879/+files/gnome-keyring_3.14.0-1ubuntu1%2Bsero1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
*** This bug is a duplicate of bug 913352 ***
https://bugs.launchpad.net/bugs/913352
** This bug has been marked a duplicate of bug 913352
package libgcr-3-common 3.2.2-1ubuntu2 failed to install/upgrade: попытка
перезаписать «/usr/share/gcr-3/ui/gcr-import-dialog.ui», который уже имеется
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400662
Tit
*** This bug is a duplicate of bug 1400662 ***
https://bugs.launchpad.net/bugs/1400662
** This bug has been marked a duplicate of bug 1400662
[vivid] upstart: gnome-keyring-gpg main process (1504) terminated with
status 2
--
You received this bug notification because you are a member of
Ok, I've figured it out. "if" without "then" in upstart jobs:
/usr/share/upstart/sessions/gnome-keyring-{gpg,ssh}.conf
Attached patch fixes it.
** Patch added: "gnome-keyring-upstart.diff"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1400662/+attachment/4287425/+files/gnome-ke
** Attachment added: "Configuration.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1400662/+attachment/4287091/+files/Configuration.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Affects me too.
** Attachment added: "Apport.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1400662/+attachment/4287090/+files/Apport.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
The last security update of nvidia-libopencl1-331-updates pulls with it
a lot of packages including X server.
The culprit seems to be this line in the changelog:
* debian/templates/control.in:
- Make libcuda1-$flavour depend on nvidia-$flavour-uvm.
that corresponds to t
Correction.
APT::AutoRemove::RecommendsImportant and APT::AutoRemove::SuggestsImportant are
only used by aptitude. apt-get just recycles the values of
APT::Install-Recommends and APT::Install-Suggests when deciding which packages
should be autoremoved. apt-get's behaviour is also affected by an
Link to yet another forum thread:
http://ubuntuforums.org/showthread.php?t=2256479
The problem is twofold.
1) Users not paying attention to apt-get saying:
The following packages were automatically installed and are no longer required:
...
Use 'apt-get autoremove' to remove them.
like in the t
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038749
Title:
update-manager could not calculate update
To manage notifications about this bug go to:
https://bugs.launchpad.ne
*** This bug is a duplicate of bug 1038749 ***
https://bugs.launchpad.net/bugs/1038749
** This bug is no longer a duplicate of bug 1022756
Update to 2.34.3
** This bug has been marked a duplicate of bug 1038749
update-manager could not calculate update
--
You received this bug notifica
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
drops dependency on gawk. The first version of the patch repl
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
drops dependency on gawk. The first version of the patch repl
** Description changed:
Option -s/--sort is supposed to sort the output, but doesn't. Attached
diff fixes the problem.
Actually, the patch fixes two unrelated bugs. One prevents sorting
altogether, another one shows up only when specifying several sorting
fields. The patch uses 'delet
** Description changed:
dpkg-awk has a two-letter short option -rs to set record separator, but
/usr/share/awk/getlong.awk only allows one-letter short options as
arguments to dpkg-awk. The equivalent long option --rec_sep works as
advertised.
- Attached diff enables two-letter short o
Public bug reported:
Option -s/--sort is supposed to sort the output, but doesn't. Attached
diff fixes the problem.
Actually, the patch fixes two unrelated bugs. One prevents sorting
altogether, another one shows up only when specifying several sorting
fields. The patch uses 'delete array' which
Public bug reported:
dpkg-awk has a two-letter short option -rs to set record separator, but
/usr/share/awk/getlong.awk only allows one-letter short options as
arguments to dpkg-awk. The equivalent long option --rec_sep works as
advertised.
Attached diff enables two-letter short options for dpk
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
drops dependency on gawk. The first version of the patch repl
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
drops dependency on gawk. The first version of the patch repl
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
drops dependency on gawk. The first version of the patch repl
** Description changed:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
- replaces dependency on gawk with dependency on virtual packag
Previous version of this patch replaced dependency on gawk with awk, but
one of the packages providing awk, mawk has priority 'required' and that
makes this dependency unneeded.
** Summary changed:
- Should depend on awk, not on gawk
+ Dependency on gawk should be dropped
** Patch removed: "repl
** Also affects: dpkg-awk (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1092539
Title:
Should depend on awk, not on gawk
To manage notifications
Public bug reported:
The only feature used by dpkg-awk beyond those required by POSIX is
'delete array'. This extension is supported by all awk variants
currently in Debian, i.e. by gawk, mawk, and original-awk. Attached diff
replaces dependency on gawk with dependency on virtual package awk
provi
** Description changed:
Binary package hint: autofs5
I've recently upgraded to lucid from lucid-beta. autofs5 was among
upgraded packages. After upgrade and reboot automounting user home
directory over NIS on login didn't work: the automounter deamon wasn't
started. After starting it
** Tags added: lucid
--
upstart job for autofs5 doesn't work on bootup
https://bugs.launchpad.net/bugs/576937
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.ubuntu.
Public bug reported:
Binary package hint: autofs5
I've recently upgraded to lucid from lucid-beta. autofs5 was among
upgraded packages. After upgrade and reboot automounting user home
directory over NIS on login didn't work: the automounter deamon wasn't
started. After starting it manually with '
rawdog in karmic was recently auto-synced with Debian:
https://launchpad.net/ubuntu/karmic/+source/rawdog/2.12.dfsg.1-1
The new version from Debian fixes this bug in karmic as for
incompatibilities with python 2.6. As previously said, I'm not sure, we
should consider the lack of a working config f
> No /home/bdmurray/.rawdog directory
I'm not sure this is a bug.
>From /usr/share/doc/README.Debian:
"In order to use rawdog, you must create a configuration file named
~/.rawdog/config"
--
Rawdog isn't runnable (incompatibilities with python 2.6)
https://bugs.launchpad.net/bugs/350920
You re
Sorry, there was a typo in the upstream patch 'as.patch'. Use the patch from
this comment instead. Or apply the upstream patch
http://offog.org/darcs/rawdog/_darcs/patches/20090130100216-cee84-267df61dcfdf2650d1b06bbf2632178f48ab8f5c.gz
on top of the 'as.patch' from my previous comment.
** Attac
I've extracted the relevant upstream patches from the darcs repository
as unified diffs. 'as.patch' applies cleanly against rawdog 2.11-1. To
apply 'hashlib.patch' use 'patch -F3'.
** Attachment added: "as.patch"
http://launchpadlibrarian.net/25026338/as.patch
** Attachment added: "hashlib.pa
** Tags added: python2.6
--
Rawdog isn't runnable (incompatibilities with python 2.6)
https://bugs.launchpad.net/bugs/350920
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:
** Summary changed:
- Rawdog isn't runnable (syntax error and more)
+ Rawdog isn't runnable (incompatibilities with python 2.6)
** Description changed:
Binary package hint: rawdog
~$ rawdog
Traceback (most recent call last):
File "/usr/bin/rawdog", line 20, in
from rawdoglib.
** Tags added: cherry-pick jaunty
--
Rawdog isn't runnable (syntax error and more)
https://bugs.launchpad.net/bugs/350920
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://l
I've just checked with the upstream. Both problems are already fixed in
rawdog-2.12. The best approach, IMHO, would be to backport these two
patches from upstream:
Use hashlib rather than sha where available.
http://offog.org/darcs/rawdog/_darcs/patches/20090130092734-cee84-6636ebd6512d04e16fd4b57
Your rawdog.py still emits warning about use of deprecated module sha
instead of hashlib. Here is my take on it.
** Attachment added: "as_and_hashlib.patch"
http://launchpadlibrarian.net/25008710/as_and_hashlib.patch
--
Rawdog isn't runnable (syntax error and more)
https://bugs.launchpad.net/
** Description changed:
Binary package hint: canto
Canto was obviously last built, when python-dev still pointed to
- python2.5-dev. The package installs its modules under /usr/python2.5
+ python2.5-dev. The package installs its modules under /usr/lib/python2.5
/site-packages/canto, but p
** Description changed:
Binary package hint: canto
Canto was obviously last built, when python-dev still pointed to
python2.5-dev. The package should probably be installing its modules
- under /usr/share/canto, since they are hardly used by something besides
- Canto. But it installs them
@Jack
Well, canto as currently packaged in Jaunty doesn't work out of the box.
:( See LP bug #342504
And thank you very much for your work.
--
nrss can't parse non-UTF-8 encoded feed that contains non-ASCII characters
https://bugs.launchpad.net/bugs/319994
You received this bug notification bec
Well, rebuilding w/o *any* changes didn't work. debian/rules needs to be
adjusted for the new directory layout. See attached patch.
** Attachment added: "python2.6.patch"
http://launchpadlibrarian.net/23865371/python2.6.patch
--
Please rebuild canto
https://bugs.launchpad.net/bugs/342504
You
** Tags removed: bitesize buildd
--
Please rebuild canto
https://bugs.launchpad.net/bugs/342504
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.ubuntu.com/mailman/li
** Tags added: python
** Tags removed: sync
--
Please rebuild canto
https://bugs.launchpad.net/bugs/342504
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.ubuntu.co
before and after the workaround.
Thanks,
Sergey Romanov
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux-image-2.6.28-4-generic 2.6.28-4.11
ProcCmdLine: root=UUID=37ddd6be-875a
Public bug reported:
Binary package hint: canto
Canto was obviously last built, when python-dev still pointed to
python2.5-dev. The package should probably be installing its modules
under /usr/share/canto, since they are hardly used by something besides
Canto. But it installs them under /usr/pyth
So, where the things stand now. NRSS is abandoned upstream in favor of Canto,
so it's unlikely to get fixed there.
It hasn't got any updates since July:
http://codezen.org/cgi-bin/gitweb.cgi?p=nrss.git
Michael, who currently maintains NRSS in Debian, is probably still in
process of becoming DD. H
Just for reference:
http://flamingspork.com/talks/2007/06/eat_my_data.odp
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
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
Thanks. Well, it's actually in 2.6.29-rc7 already:
http://lwn.net/Articles/321778/
--
Logitech USB PS/2 mouse is mistaken for Elantech Touchpad
https://bugs.launchpad.net/bugs/318722
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Yes, the patched kernel is for jaunty, but you don't need to change to
jaunty to try it out. Simply download the linux-image .deb file for your
architecture (i386 or amd64) and install it with gdebi or with dpkg -i
then reboot into the new kernel.
--
Elantech touchpad is incorrectly recogonised a
Could you please also check if it works with this kernel, patched for the bug
LP#318722?
http://people.ubuntu.com/~apw/lp318722-jaunty/
--
Elantech touchpad is incorrectly recogonised as a "ImPS/2 Logitech Wheel Mouse"
https://bugs.launchpad.net/bugs/123775
You received this bug notification be
Yep, it works for me. dmesg output attached. I'm also sending a comment
to the folks with real Elantech hardware, affected by LP#123775 to check
out that this fix doesn't bring any regressions to them.
** Attachment added: "dmesg.txt"
http://launchpadlibrarian.net/21622600/dmesg.txt
--
Logite
** Attachment added: "encoding.patch"
http://launchpadlibrarian.net/21533528/encoding.patch
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21533529/Dependencies.txt
--
nrss can't parse non-UTF-8 encoded feed that contains non-ASCII characters
https://bugs.launchpad.
Public bug reported:
Binary package hint: nrss
nrss 0.3.9-1 gets an error parsing a feed encoded in ISO 8859-1 that
contains international symbols. Sometimes only the first item get
displayed if it contains no accented characters.
I've tried this feed:
http://rss.golem.de/rss.php?feed=RSS2.0
Bu
** Tags added: elantech mouse
--
Logitech USB PS/2 mouse is mistaken for Elantech Touchpad
https://bugs.launchpad.net/bugs/318722
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
h
'udevadm info --attribute-walk' output for the mouse attached on USB port.
VendorID=046D, ProductID=C03E
** Attachment added: "udevadm-info-attr-usb.txt"
http://launchpadlibrarian.net/21362103/udevadm-info-attr-usb.txt
--
Logitech USB PS/2 mouse is mistaken for Elantech Touchpad
https://bugs.
'udevadm info --attribute-walk' output for the mouse attached on PS/2 port.
VendorID=0002, ProductID=000E
** Attachment added: "udevadm-info-attr-ps2.txt"
http://launchpadlibrarian.net/21362082/udevadm-info-attr-ps2.txt
--
Logitech USB PS/2 mouse is mistaken for Elantech Touchpad
https://bugs
Some additional infos
Mouse model is M-BT58
The mouse is misindentified only if attached over PS/2 adapter. If
attached directly on an USB port, then it is recognised properly as
Logitech USB-PS/2 Optical Mouse (lshal output for this case attached).
** Attachment added: "lshal-usb.txt"
http:/
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/21353022/lshal.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/21353023/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/21353024/CurrentDmesg.txt
** Attachment adde
o add line
options psmouse proto=imps
into /etc/modprobe.d/options
and it works.
I've attached lshal output before and after the workaround.
Thanks,
Sergey Romanov
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.
** Tags added: hardy
--
error after upgrading to distinct package: bash: complete: kpdf: no completion
specification
https://bugs.launchpad.net/bugs/190619
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
Well, I have just tested and found that kpdf can't handle compressed formats.
So, really you should remove kpdf from the line #84 too, and add this line
after it:
complete -f -X '!*.@(?(e)ps|?(E)PS|pdf|PDF)' kpdf
--
error after upgrading to distinct package: bash: complete: kpdf: no completion
'kpdf' should be deleted from the end of the line #88 in
/etc/bash_completion, since it is now redefined in the line #84.
That means,
complete -f -X '!*.@(pdf|PDF)' acroread gpdf xpdf kpdf
should now be
complete -f -X '!*.@(pdf|PDF)' acroread gpdf xpdf
--
error after upgrading to distinct pac
Public bug reported:
The only reason showfsck uses #!/bin/bash instead of #!/bin/sh is
arithmetic evaluation.
The line NB=$(($MMC - $MC + 1)) in /usr/sbin/showfsck can be changed to
NB=$(expr $MMC - $MC + 1) to make the script shell-agnostic.
/usr/bin/expr is in coreutils package, which has prior
Public bug reported:
Binary package hint: nrss
Package nrss (version 0.3.1-1 from universe) can't read any of the feeds
I tried so far.:
Config file ~/.nrss/config:
add "http://lwn.net/headlines/newrss"; "LWN"
Error message:
Error Updating http://lwn.net/headlines/newrss
I've downloaded versio
quick & dirty debian package that I made for 0.3.8 by copying debian
directory from nrss-0.3.1 and adding one record to the changelog.
** Attachment added: "nrss_0.3.8-0~sr1_i386.deb"
http://launchpadlibrarian.net/11593600/nrss_0.3.8-0%7Esr1_i386.deb
** Tags added: 8.04
** Summary changed:
-
** Description changed:
- With upload of OOo 2.3.1 noone of l10n packages can be installed,
- because of Depends: openoffice.org-common (< 1: 2.3.0.1)
+ With upload of OOo 2.3.1 none of l10n packages can be installed, because
+ of Depends: openoffice.org-common (< 1: 2.3.0.1)
+
+ The bug can be c
** Description changed:
With upload of OOo 2.3.1 noone of l10n packages can be installed,
- because of Depends: openoffice.org (< 1: 2.3.0.1)
+ because of Depends: openoffice.org-core (< 1: 2.3.0.1)
** Description changed:
With upload of OOo 2.3.1 noone of l10n packages can be installed,
- b
Should be Depends: openoffice.org-common (< 1:2.3.0.1)
--
Hardy: dependency on openoffice.org-common is too tight
https://bugs.launchpad.net/bugs/183769
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
Public bug reported:
With upload of OOo 2.3.1 noone of l10n packages can be installed,
because of Depends: openoffice.org (< 1: 2.3.0.1)
** Affects: openoffice.org-l10n (Ubuntu)
Importance: Undecided
Status: New
--
Hardy: dependency on openoffice.org-common is too tight
https://bu
The problem isn't limited to Firefox only, nor to applications that use pango
(like Firefox and Abiword do). E.g. Opera, which I believe doesn't use pango,
exibits the same behaviour. It's due to some complex interaction between the
used font and application, so with some unlucky combinations o
The version 2.0-1 of package 'ttf-arabeyes' still has this problem for two of
its fonts: ae_AlYarmook and ae_Sindbad.
These fonts' names and paths are incorrectly spelled in
/etc/defoma/hints/ttf-arabeyes.hints, which results in broken links in
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType:
I have had a something similar problem in Debian etch. An NTFS-formatted USB
drive *would* actuallly get mounted, but I couldn't browse the filesystem or
change into it as normal user (only as root) and Konqueror gave that same
message: 'hal-storage-removable-mount-all-options refused uid '.
Public bug reported:
Binary package hint: lirc-modules-source
See debian bug #400494. Could you please apply the patch from that bug?
So I don't have to do touch /usr/src/linux/include/linux/config.h any
more.
Thanks.
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: Unconfi
76 matches
Mail list logo
