** Also affects: e2fsprogs (Debian) via
http://sourceforge.net/support/tracker.php?aid=2927365
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #564084
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564084
** Changed in: e2fsprogs
Remote watch:
** Bug watch added: SourceForge.net Tracker #2927365
http://sourceforge.net/support/tracker.php?aid=2927365
** Also affects: e2fsprogs via
http://sourceforge.net/support/tracker.php?aid=2927365
Importance: Unknown
Status: Unknown
--
debugfs: logdump -bblock show incorrect
** Changed in: e2fsprogs (Ubuntu)
Assignee: (unassigned) = Anon Sricharoenchai (anon-hui)
--
debugfs: logdump -bblock show incorrect allocation status in block bitmap
https://bugs.launchpad.net/bugs/501686
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: e2fsprogs (Ubuntu)
Assignee: Anon Sricharoenchai (anon-hui) = (unassigned)
--
debugfs: logdump -bblock show incorrect allocation status in block bitmap
https://bugs.launchpad.net/bugs/501686
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: e2fsprogs
logdump -bblock command in debugfs show incorrect allocation status
in block bitmap
== Step to repeat ==
$ debugfs /dev/sda1
debugfs: logdump -b1827766
== What happens ==
It always report block is SET like this,
FS block 1802240 logged at
** Attachment added:
e2fsprogs-1.41.9-1ubuntu3.logdump-bitmap_offset_to_dump.patch
http://launchpadlibrarian.net/37292002/e2fsprogs-1.41.9-1ubuntu3.logdump-bitmap_offset_to_dump.patch
--
debugfs: logdump -bblock show incorrect allocation status in block bitmap
Public bug reported:
Binary package hint: apt
apt-get -s should not lock /var/lib/dpkg/lock, so that it can be run
without root permission.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
apt-get -s should not lock /var/lib/dpkg/lock
Public bug reported:
Package: db4.6-util
Severity: normal
*** Please type your report below this line ***
The command db_dump, db_load, and db_ are missing.
Should update-alternatives to make symlink like this,
* db_dump -- db4.6_dump
* db_load -- db4.6_load
* db_ -- db4.6_
*
Public bug reported:
Binary package hint: rrdcollect
In file /etc/init.d/rrdcollect, restart section,
echo -n Restarting $DESC: $NAME
- start-stop-daemon --stop --quiet --pidfile --make-pidfile \
+ start-stop-daemon --stop --quiet --pidfile \
Public bug reported:
Binary package hint: bash-completion
Completion for zcmp zdiff zegrep zfgrep zgrep zless zmore should allow
all file types, since they can process both gzip and non gzip files.
/etc/bash_completion:
-complete -f -X '!*.@(Z|gz|tgz|Gz|dz)' gunzip zcmp zdiff zcat zegrep
It is already fixed in the latest version.
** Changed in: bash-completion (Ubuntu)
Status: New = Fix Committed
--
Completion for zcmp zdiff zegrep zfgrep zgrep zless zmore should allow all
file types
https://bugs.launchpad.net/bugs/435020
You received this bug notification because you
The latest version only allow the pattern *.*, while it should be *
** Changed in: bash-completion (Ubuntu)
Status: Fix Committed = New
--
Completion for zcmp zdiff zegrep zfgrep zgrep zless zmore should allow all
file types
https://bugs.launchpad.net/bugs/435020
You received this bug
Given the sensitivity of escaping code in general, could you submit it on
the SBLIM bugtracker so that the issue gets reviewed and discussed by
upstream developers ?
Done,
https://sourceforge.net/tracker/?func=detailaid=2805214group_id=128809atid=712784
Furthermore, do you see an easy
$ wbemcli gi
'http://user:p...@hostname/root/cimv2:Win32_Share.Name=test;'
hostname:5988/root/cimv2:...,Caption=test\Test\,Descriptiontest...
Some typo in the above output (missing = after Description),
$ wbemcli gi 'http://user:p...@hostname/root/cimv2:Win32_Share.Name=test;'
Public bug reported:
According to the function Cimom::unescapeXml() in CimXml.cpp, in addition to
escaping the quote character, it should also escape the backslash character.
Without escaping backslash, if the string is ended with backslash,
the quoted text output will be ambiguous. The
On 3/17/09, Launchpad Bug Tracker 150...@bugs.launchpad.net wrote:
This bug was fixed in the package tasksel - 2.73ubuntu17
---
tasksel (2.73ubuntu17) jaunty; urgency=low
* Avoid removing packages that are in other tasks that are still selected
or not displayed (LP:
I mean, it is resolved by,
1. changing the program logic in tasksel?, or by
2. remove the common and/or library packages from the tasks (such as,
lamp task)?
On 3/24/09, Colin Watson cjwat...@canonical.com wrote:
On Tue, Mar 24, 2009 at 12:47:01PM -, Anon Sricharoenchai wrote:
On 3/17/09
On 3/24/09, Colin Watson cjwat...@canonical.com wrote:
On Tue, Mar 24, 2009 at 02:32:14PM -, Anon Sricharoenchai wrote:
I mean, it is resolved by,
1. changing the program logic in tasksel?, or by
2. remove the common and/or library packages from the tasks (such as,
lamp task
Public bug reported:
$ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
1. Since some packages, for example, libpq5, mysql-common are in both
lamp-server and mail-server task
2. invoking tasksel remove mail-server will remove libpq5, mysql-common
* removing libpq5 causing apache2 to be
Public bug reported:
Binary package hint: virtualbox-ose
$ lsb_release -rd
Description:Ubuntu 8.04.1
Release:8.04
Package: virtualbox-ose
Version: 1.5.6-dfsg-6ubuntu1
Severity: serious
Justification: no longer builds from source
*** Please type your report below this line ***
==
I found the same problem in hardy version,
== Steps to reproduce ==
1. boot into ubuntu 8.04.1 live DVD
2. $ aptitude install devscripts build-essential fakeroot
$ dget
http://archive.ubuntu.com/ubuntu/pool/universe/v/virtualbox-ose/virtualbox-ose_1.5.6-dfsg-6ubuntu1.dsc
$ dpkg-source -x
--- Daniel Holbach [EMAIL PROTECTED] wrote:
The patch adds API - is it included upstream already?
Not yet, I think, since I see no any response from the upstream authors, after
I've sent the patch
to them.
** Changed in: libmms (Ubuntu)
Status: Unconfirmed = Needs Info
--
Yes, it only apply to mimms 0.0.9.
The latest mimms 2.0.0 is redesigned to use libmimms, so this buffer overflow
(as indicated in this patch) may not present in 2.0.0.
--
patch to fix many buffer overflows vulnerability
https://launchpad.net/bugs/50932
--
ubuntu-bugs mailing list
23 matches
Mail list logo
