Package: initscripts
Version: 2.86.ds1-6
Severity: normal
Tags: patch
The /etc/init.d/checkroot.sh script ignored the fsck's PLEASE REBOOT
LINUX NOW exit code because the code is stored too late. As a result,
the fixes fsck made to my filesystem could be corrupted again because
the system
Package: libnss-ldap
Version: 220-1
Followup-For: Bug #277640
The stall happens because libnss-ldap is linked against the
non-reentrant version of the OpenLDAP library. This causes an
application's call to gethostbyname() to lock up because another call to
gethostbyname() occurs within the
Package: postgresql-dev
Version: 7.4.7-3
Followup-For: Bug #264603
It would be nice to get the recent 8.0 stable branch of the PostgresQL
client library (currently provided by the postgresql-dev package)
because the upstream fixed a bug in the error reporting code:
Here is another work-around to setting stdout's encoding.
import sys, codecs, locale
if sys.stdout.encoding is None:
(lang, enc) = locale.getdefaultlocale()
if enc is not None:
(e, d, sr, sw) = codecs.lookup(enc)
# sw will encode Unicode data to the
My report on wodim failure could be a result of my own liberal
application of hdparm. Few days later I removed /etc/hdparm.conf,
rebooted the machine and found wodim working just fine.
The hdparm options that failed my system are included below. My
DVD writer is /dev/hdb. Regards,
--
Ilguiz
On Mon, Apr 16, 2007 at 01:51:05AM -0400, Ilguiz Latypov wrote:
My report on wodim failure could be a result of my own liberal
application of hdparm.
I am mistaken again, so my former report on the failure in wodim
remains in force.
I found that wodim still produced blank DVDs even after I
$HWCLOCKPARS.
Without the above fix, the hwclock* scripts will assume that the
system time was updated from the hardware clock and that the
hardware clock is UTC-based. Then the scripts will apply a
timezone shift. This will make the current system time shifted
incorrectly.
--
Ilguiz Latypov
programmer
Package: python-central
Version: 0.5.13
Followup-For: Bug #418108
I am guessing that the fix to the problem can be as simple as adding a
line global config under global _defaults in the failed script:
--- /usr/share/pycentral-data/pyversions.py.orig2007-04-06
23:23:10.0 -0400
Package: wodim
Version: 9:1.1.4-1
Followup-For: Bug #396194
I have a similar problem here. I created the ISO image with
vobcopy 0.5.14
dvdauthor 0.6.14
genisoimage 1.1.4
$ mkdir vobs
$ vobcopy -o vobs
$ mkdir dvd
$ dvdauthor -o dvd -t vobs/*.vob
$ dvdauthor -o dvd -T
$ genisoimage -dvd-video
The other DVD-burn command produced a working disk with the same
ISO image.
$ genisoimage -dvd-video -o /dev/dvdrw bv.iso
--
Ilguiz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: x11-common
Version: 1:7.0.22
Followup-For: Bug #226180
It occured to me that the readline mode of Debian configurator,
DEBCONF_FRONTEND=readline dpkg-reconfigure
will show default prompts when libterm-readline-gnu-perl is installed.
This was suggested by debconf(7) from
Package: yaird
Version: 0.0.12-14
Followup-For: Bug #345374
Same problem here with via82cxxx not being included into /init.
As a work-around, I modified /etc/yaird/Default.cfg to include
the chipset-specific IDE driver unconditionally in the prologue:
Jonas,
On Thu, Jun 29, 2006 at 12:19:45PM +0200, Jonas Smedegaard wrote:
Which kernel package do you use? Is it an official Debian-packaged one?
2.6.17. I am running Debian unstable. The package was retrieved
through the regular Debian mechanism (apt-get from
debian.yorku.ca).
And what
Package: x11-common
Version: 1:7.0.22
Severity: important
Tags: patch
Trying to figure why my choice of ImPS/2 isn't stored in xorg.conf,
I found that dexconf ignored it. Here is the patch.
===
--- dexconf.orig2006-06-11
See also bug 511633.
--
I.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Perhaps, my issue is related. I am getting intermittent no error
errors displaying status: 0x02 (CHECK_CONDITION).
I suspect that an extra resid: 28 in addition to a regular resid: 8 is an
early indicator of the trouble.
As a result, the
Package: wodim
Version: 9:1.1.10-1
Severity: normal
Forgot to add the dmesg output that might be related. Also, I just realized
that the sense code error message was logical block address out of range.
[ 4469.846681] hdb: command error: status=0x51 { DriveReady SeekComplete Error }
[
Package: python2.5-minimal
Version: 2.5.5-5
Severity: normal
I wonder if this can be fixed with the following change,
--- /usr/lib/python2.5/py_compile.py.orig 2010-04-21 06:00:38.0 -0400
+++ /usr/lib/python2.5/py_compile.py2010-04-21 05:46:52.0 -0400
@@ -153,6 +153,7 @@
Package: reportbug
Version: 4.12
Severity: normal
This appears to be a result of an extra word obsolete in addition to
filename and md5sum fields of a conffiles record. Reproduced when
reporting on python2.5-minimal.
=
Thanks for the proposed patch. Anyhow, the right solution is to simply
ignore that extra value in the module that parses them [..]
conffiles = conffiles + [tuple(line.split()[:2])]
Nice. Thanks, Sandro.
--
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Package: update-manager-gnome
Version: 0.200.3-1
Severity: grave
File: /usr/share/pyshared/UpdateManager/Frontend/Gtk/ui.py
Tags: sid
Justification: renders package unusable
Update Manager crashed on its start.
*** /tmp/update-manager-bugm_Su6p
The information below has been automatically
Package: linux-2.6
Version: 2.6.32-30
Severity: critical
Justification: breaks the whole system
Both normal and safe boot modes panicked when running the ram disk
image. Worse, the upgrade DELETED the earlier kernel image and ram disk
image. I managed to boot by editing the safe mode command
Package: linux-2.6
Version: 2.6.38-3
Severity: critical
Justification: breaks the whole system
Booting panics when bringing interfaces up, including a Wi-Fi adm8211
from drivers/net/wireless. The stack trace mentions
ieee80211_rx_handlers in mac80211, net_receive_skb, do_page_fault,
Thanks for quashing my hasty conclusion about the timing of the kernel crash.
I now see that the crash occurred after the ramdisk stage succeeded. Probably,
this may have something to do with memory paging to disk. I could boot to the
shell, disable swapping, launch udev, resolvconf,
Contrary to my earlier conclusion, the upgrade did not delete
older images. It appears a ramdisk generation change may have
included a bad module whose loading crashed the system later.
I could not boot other images because my Grub 2 configuration file
grub.cfg missed the corresponding initrd
On 27/06/12 07:57 PM, Ilguiz Latypov wrote:
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
After reporting my work-around I followed advice of the davmail author
and disabled the use of system proxy settings
I worked around the crash by choosing Open JDK 1.7 to run davmail
compiled by Open JDK 1.6.
sudo update-alternatives --config java
I believe it is possible that davmail could compile with Open JDK 1.7
and that its build system prevents higher version numbers by mistake.
I believe changing the
Package: debian-installer
Version: i386 netinst as of October 5, 2011
Severity: important
Tags: d-i
Dear Maintainer,
* What led up to the situation?
I decided to install Debian on a new disk drive and preserve the Windows
installation on the original drive.
I downloaded the latest
Package: dosfstools
Version: 3.0.13-1
Followup-For: Bug #691093
Dear Maintainer,
Same here.
* What led up to the situation? Checking the filesystem of a micro SD card.
* What exactly did you do (or not do) that was effective (or
ineffective)? I ran sudo fsck /dev/sdc1 -a.
* What
Running dosfsck -r PARTITION works around the crash.
--
-
This transmission (including any attachments) may contain confidential
information, privileged material (including material protected by the
solicitor-client or other
Package: gnash
Version: 0.8.10
The --enable-avm2 option causes a warning in the configure script saying that
the script did not recognize the option. I found that configure.ac commented
out its handling by putting dnl at the beginning of each line. Removing the
dnl (delete to new line?)
Package: smbclient
Version: 2:3.6.13-1
Severity: minor
Dear Maintainer,
* What led up to the situation?
Ran smbclient -A /etc/credentials-USER -L HOST.example.net
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran the above command.
* What
Package: basez
Version: 1.6-3
Severity: important
Tags: upstream
Dear Maintainer,
* Decoding a JWT signature showed that omitting the padding (as
required by one of the JWS RFC) causes a failure in base64url -d.
$ echo -n
Sorry it failed even with the padding, so I don't know what is failing
in basez.
I contacted the author and he pointed to the "-a" option that controls
the search behaviour. I found the "-A" option to follow my expectation
of a forward and backward search,
-a or --search-skip-screen
By default, forward searches start at the top of the displayed
35 matches
Mail list logo
