Package: haveged
Version: 1.9.1-5
Severity: important
Dear maintainer,
Haveged fails to start often (but not always) during boot. Manually starting
it later with "systemctl start haveged" is successful. Systemd version is
232-19. Journalctl showed the following error message:
systemd[557]: hav
Package: initramfs-tools-core
Version: 0.127
Severity: serious
Justification: Policy 3.5
I tried a partial upgrade of initramfs-tools, but it failed, complaining that
busybox was too old, see console messages below. The version of busybox
installed at that time was 1:1.22.0-9+deb8u1. I solved this
Package: kstars
Version: 4:16.08.3-1
Severity: serious
Justification: Policy 3.5
If libqt5sql5-sqlite is not installed, starting kstars produces a popup
window with this message:
The file citydb.sqlite could not be found. KStars cannot run properly
without this file. KStars searches for this
Package: kstars-data-extra-tycho2
Version: 1.1r1-9
Severity: grave
Justification: renders package unusable
The current testing version of kstars, version 4:16.08.3-1, expects
deepstars.dat to reside in /usr/share/kstars along with its other data files.
However, the current testing version of kstar
Package: efibootmgr
Version: 0.11.0-1
Severity: serious
Justification: Policy 4.9
Dear Maintainer,
I used "dpkg-buildpackage -b" to build efibootmgr and it has created
efibootmgr in /usr/sbin (in addition to building the .deb package).
Here's a snippet from the build log, note the "Installed Fil
I've just tested with efibootmgr 0.5.4-3 (the current stable version) and
it can list the boot entries. strace shows that it receives an EIO error,
but it doesn't cause the program to abort.
--
Jan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubsc
Package: efibootmgr
Version: 0.11.0-1
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
On my system, reading Boot0005 fails with EIO:
openat(AT_FDCWD, "/sys/firmware/efi/vars/",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
brk(0) = 0x
On Wed, Oct 29, 2014 at 12:11:18PM -0500, D. Jared Dominguez wrote:
> Can you confirm whether this is still an issue for you? New versions
> of libefivar0 are in testing and unstable. Please test against them.
The segmentation fault still occurs with libefivar0 version 0.15-1 and
efibootmgr versio
Package: libefivar0
Version: 0.12-1
Severity: critical
Justification: breaks the whole system
Upgrading libefivar0 from version 0.10-5 to 0.12-1 causes a segmentation
fault when running efibootmgr without arguments (I tried it with both
efibootmgr 0.7.0-2 and 0.9.0-1). I'm not quite sure if sever
Package: mdadm
Version: 3.3.2-1
Severity: minor
Tags: patch
While setting up a new system, I noticed an incorrect value in the output
of mdadm --examine:
Avail Dev Size : 2095080 (1023.16 MiB 1072.68 MB)
The 1023.16 MiB were quite irritating because the underlying partition has
a size of exact
Package: gnome-settings-daemon
Version: 3.4.2-4+b1
Severity: important
gdm3 + xfce4
After booting, the gdm3 login screen is black with a small grey login window,
but I can login.
After logging out, or after /etc/init.d/gdm3 stop && /etc/init.d/gdm3 start, I
usually get the "Oh No! Something has
On Fri, Jul 29, 2011 at 05:18:48PM +0200, Moritz Mühlenhoff wrote:
> Does this still occur with current kernels?
I don't get this warning anymore since updating from 3.2.6-1 to 3.2.7-1.
--
Jan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe
On Fri, Jul 29, 2011 at 05:18:48PM +0200, Moritz Mühlenhoff wrote:
> Does this still occur with current kernels?
Yes. Here's a warning from kernel version 3.0.0-1:
[1.984004] [ cut here ]
[1.984009] WARNING: at
/build/buildd-linux-2.6_3.0.0-1-i386-ML66CU/linux-2.
On Thu, Jul 29, 2010 at 06:02:41PM +0100, Ben Hutchings wrote:
> Let us know the bug number or URL so that we can track it.
https://bugzilla.kernel.org/show_bug.cgi?id=16481
--
Jan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Mon, Jul 26, 2010 at 06:44:25PM +1000, Neil Brown wrote:
> If you are up to compiling and installing your own mdadm, could you try
> reverting
>
> http://neil.brown.name/git?p=mdadm;a=commitdiff;h=319767b85c2b16d80c235195329470c46d4547b3
>
> from 3.1.2 and see if the makes the difference?
It
Package: linux-2.6
Version: 2.6.32-18
Severity: minor
I'm getting this warning for quite a while now, but not on every boot.
Stack traces below ide_pci_init_two differ slightly. I've also tried
the current experimental kernel, but the warning is still there (although
the stack trace is somewhat d
Package: mdadm
Version: 3.1.2-2
Severity: normal
I get an udevadm settle timeout during boot after upgrading mdadm from
version 3.1.1-1 to 3.1.2-2:
> Success: assembled all arrays.
> done.
> [ 12.509710] device-mapper: uevent: version 1.0.3
> [ 12.523034] device-mapper: ioctl: 4.15.0-ioctl (2
Package: sane
Version: 1.0.14-8
Severity: important
Tags: patch
xscanimage crashes at startup in gtkglue.c:option_menu_lookup(), called by
gtkglue.c:panel_build(), when trying to create the DPI selection widget.
The DPI list in opt->constraint.word_list contains 32 values from 50 to 2400,
but the
I have the same problem on a Dell Latitude D630. Brightness seems to be
set through hardware (stopping acpid has no effect, and stopping hal just
prevents the brightness bar from appearing on the screen when I press the
brightness keys).
Brightness reset is triggered by gnome-screensaver. Messag
On Fri, Aug 29, 2008 at 07:21:43AM +0200, Brice Goglin wrote:
> You should first try reverting
> http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-ati.git;a=commitdiff;h=15536739b0e68e25dbd89d5d517680d855077fab;hp=2ca76841ecb89133d8897db1aa540219a565aebc
Reverting this one fixes the prob
Package: xserver-xorg-video-radeon
Version: 1:6.9.0-1+lenny3
Severity: important
xine shows flickering horizontal bands of greenish noise that cover most
of the screen (or window if not playing in fullscreen mode). Downgrading
to 1:6.9.0-1+lenny2 makes the problem disappear, as does configuring x
Package: libgphoto2-2
Version: 2.4.1-1
Severity: normal
libgphoto2's udev rules for my USB camera didn't match anymore after I
upgraded libgphoto2-2 from 2.4.0-9 to 2.4.1-1. Upgrading udev from
0.105-4 (etch) to 0.124-3 (sid) fixed that problem.
/etc/udev/libgphoto2.rules uses SUBSYSTEM!="usb|us
On Wed, Jan 30, 2008 at 07:27:24AM +0100, Reinhard Tartler wrote:
> This patch is currently being discussed upstream:
>
> http://thread.gmane.org/gmane.comp.video.xine.devel/17764
The patch discussed in that thread does not seem to have anything in
common with 03-udf.dpatch in libdvdread-0.9.7-6.
Package: libxine1-misc-plugins
Version: 1.1.10-1
xine-lib has trouble playing some new DVDs with incorrect UDF file systems.
It uses the same code as libdvdread. libdvdread-0.9.7-6 has been patched
to handle these DVDs (see bug #460400).
Please consider applying that patch to xine-lib as well.
Package: yaird
Version: 0.0.12-24
yaird fails with the following message since I upgraded the kernel to 2.6.23:
yaird error: bad device link in /sys/class/input/event0/device (fatal)
> ls -l /sys/class/input/event0/device
lrwxrwxrwx 1 root root 0 Dec 11 14:01 /sys/class/input/event0/device ->
The version of bash that failed for me in Bug#297137 was 2.05a-11.
The version in the Depends field in hotplug-0.0.20040329-20 is 2.05-0beta1
which is OLDER than 2.05a-11. The comment in Bug#300113 speaks of version
2.05b-beta1 which doesn't exist. The changelog entry for version 2.05b-1
suggests
On Sun, Feb 27, 2005 at 01:34:20PM +0100, Marco d'Itri wrote:
> I tested this script with bash, dash and even posh, and it works fine.
>
> #!/bin/sh -e
> echo a
> unset no_such_variable1 no_such_variable2
> echo b
[EMAIL PROTECTED]:~$ ./testunset.sh
a
[EMAIL PROTECTED]:~$ dpkg -S /bin/sh
bash: /
Package: hotplug
Version: 0.0.20040329-17
Severity: grave
Tags: patch
Justification: renders package unusable
"/etc/init.d/hotplug start" aborts almost immediately, it doesn't even
print the "Starting hotplug subsystem" message. I didn't notice this
until I tried to use an USB device and found t
28 matches
Mail list logo