Bug#1027937: gwenview: Under Bookworm, Gwenview no longer displays NEF images (RAW images)
Package: gwenview Version: 4:22.12.0-1+b1 Severity: important X-Debbugs-Cc: crop...@acm.org -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/64 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gwenview depends on: ii kinit 5.101.0-1 ii kio5.101.0-2 ii libc6 2.36-7 ii libcfitsio10 4.2.0-3 ii libexiv2-270.27.5-4 ii libgcc-s1 12.2.0-11 ii libjpeg62-turbo1:2.1.2-1+b1 ii libkf5activities5 5.101.0-1 ii libkf5baloo5 5.101.0-1 ii libkf5completion5 5.101.0-1 ii libkf5configcore5 5.101.0-1 ii libkf5configgui5 5.101.0-1 ii libkf5configwidgets5 5.101.0-1 ii libkf5coreaddons5 5.101.0-1 ii libkf5filemetadata35.101.0-3 ii libkf5guiaddons5 5.101.0-1 ii libkf5i18n55.101.0-1+b1 ii libkf5iconthemes5 5.101.0-1+b1 ii libkf5itemmodels5 5.101.0-2 ii libkf5itemviews5 5.101.0-1 ii libkf5jobwidgets5 5.101.0-1 ii libkf5kdcraw5 22.12.0-2 ii libkf5kiocore5 5.101.0-2 ii libkf5kiofilewidgets5 5.101.0-2 ii libkf5kiogui5 5.101.0-2 ii libkf5kiowidgets5 5.101.0-2 ii libkf5notifications5 5.101.0-1 ii libkf5parts5 5.101.0-1 ii libkf5purpose-bin 5.101.0-1 ii libkf5purpose5 5.101.0-1 ii libkf5service-bin 5.101.0-1 ii libkf5service5 5.101.0-1 ii libkf5solid5 5.101.0-1 ii libkf5widgetsaddons5 5.101.0-1 ii libkf5xmlgui5 5.101.0-1+b1 ii libkimageannotator00.6.0-1 ii liblcms2-2 2.13.1-1+b1 ii libphonon4qt5-44:4.11.1-4 ii libpng16-161.6.39-2 ii libqt5core5a 5.15.7+dfsg-2 ii libqt5dbus55.15.7+dfsg-2 ii libqt5gui5 5.15.7+dfsg-2 ii libqt5printsupport55.15.7+dfsg-2 ii libqt5svg5 5.15.7-2 ii libqt5widgets5 5.15.7+dfsg-2 ii libqt5x11extras5 5.15.7-2 ii libstdc++6 12.2.0-11 ii libtiff5 4.4.0-6 ii libx11-6 2:1.8.3-3 ii perl 5.36.0-6 ii phonon4qt5 4:4.11.1-4 Versions of packages gwenview recommends: ii kamera 4:22.12.0-2 ii kio-extras 4:22.12.0-4 ii qt5-image-formats-plugins 5.15.7-2 gwenview suggests no packages. -- no debconf information
Bug#987441: Suggest bug 990016; easy to fix for D-I, and hits specific server boards hard
Might I suggest bug #990016 for the D-I urgency list; many of my server boards have ASPEED drivers and I've been surprised how sometimes this bites me and sometimes not. Please consider fixing this before releasing the production installer for Bullseye. Thank you.
Bug#970176: Please move f2fs-tools to version 1.14 from upstream; 1.11 does NOT support compression
Package: f2fs-tools Version: 1.11.0-1.1 I installed f2fs on a 4TB SSD. This SSD was for testing purposes to manipulate some versioned backups. When I attempted to make a new f2fs file system with compression enabled using the 'options' flag the program says invalid option. All of the upstream documentation states that this option IS supported. I am using Debian Buster, kernel 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64 GNU/Linux. Thank you for your work.
Bug#519200: K3b; BD-RE/BD-R; suggest xorriso or libburn4 for backend
Package: k3b Version: 2.0.2 Kernel: Linux (AMD64) release 3.9-0.bpo.1-amd64 Debian Wheezy 7.6 plus backports KDE: 4.8.4 wodim (9:1.1.11-2) xorriso (1.2.2-2) Dear Developers for K3b, Thank you for all your hard work and maintenance of the K3b package. I use it extensively and it usually works very well. Recently, I began to use Blu-Ray discs (BD-R, BD-RE, and BD-RE DL) for backup due to the size of my burgeoning data. At this point I discovered that many instabilities exist with cdrkit and growisofs relating to blu-ray discs of all types. Examples: i) cannot detect the disc is already formatted ii) cannot simultaneously format disc prior to sequential burn iii) is highly unstable insofar as will work one in ten times iv) size detection of disc and corresponding ISO/UDF image is erratic v) cannot perform backups such as preserving permissions very easily vi) will not burn the jigdo Debian 7.6 blu-ray discs (had to use xorriso on the command line (this is probably the easiest method to recreate the problem) BREAK --- I removed wodim (cdrkit) and installed cdrskin (the wraparound cdrecord replacement for xorriso) but K3b became even more unstable. I only got K3b to recognize cdrskin after I installed a Debian Alternatives manually. K3b never recognized cdrskin automatically. When I completed the Alternatives it made K3b less useful for buning NON-blu-ray discs; hence the reason I am submitting this bug report/update. Please consider integrating xorriso as a freestanding backend for K3b... OR Please consider using the libburn4 library as mentioned in the report from Mr. Danchev above. Thank you, Mr. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582342: Post test comments; this bug is not closed.
Folks, This bug IS in squeeze. I use the squeeze distribution and it still exists. Thanks, C. Cropper PS: Will test with recent updates in about one week. tags 582342 - squeeze thanks On Thu, 2010-07-29 at 20:37 -0400, Cropper, C. A. wrote: This bug is very real and reappeared on my system after I updated to all the squeeze versions today. I even tested the SID version of grub-pc and grub-common which also do not work. Then it shouldn't be tagged squeeze. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582342: grub-pc: recent change; bug reappears; can't load kernel under 2.6.32-5-amd64
Package: grub-pc
Version: 1.98+20100710-1
Severity: normal
A recent change made this bug reappear on my system. The DVD-drives are now on
the SATA phy ports while the hard drives are on the MPTSAS phy ports. Will
test using other parameters and report back. I had to boot the 2.6.32-3-amd64
kernel as a backup.
C. Cropper
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/md1_crypt / xfs
rw,relatime,attr2,logbsize=256k,sunit=512,swidth=1536,noquota 0 0
/dev/md0 /boot xfs rw,sync,relatime,wsync,attr2,noquota 0 0
/dev/mapper/bbox /bbox xfs rw,relatime,attr2,logbufs=8,noquota 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMBXUW
(hd1) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMNPTW
(hd2) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMVVMW
(hd3) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7HW
(hd4) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7RW
(hd5) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7VW
(hd6) /dev/disk/by-id/ieee1394-0030e002e0030182:00043c:
(hd7) /dev/disk/by-id/md-uuid-6023ec61:688f13d8:00a731dc:64f342ff
(hd8) /dev/disk/by-id/md-uuid-a8cd9021:89ac8fa3:00a731dc:64f342ff
(hd9) /dev/sda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
if loadfont /grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
insmod png
if background_image /grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/md1_crypt ro
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/md1_crypt ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-3-amd64 ...'
linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-amd64 (recovery mode)' --class
debian --class gnu-linux
Bug#582342: Post test comments; this bug is not closed.
Dear All, This bug is very real and reappeared on my system after I updated to all the squeeze versions today. I even tested the SID version of grub-pc and grub-common which also do not work. Thank you, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582342: Godel and inconsistency; never will know...; system with RAID and CRYPTO
Can this bug report be closed then? Technically, the bug was not fixed. I just rearranged some **seemingly unrelated** hardware and the bug disappeared. Overall, I don't think I can answer your question. You must understand, I am just a user of the software... not a developer. ;-) The expert developers of grub will have to decide whether to close the bug. Thanks for your work, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582342: grub-pc: cannot read the linux header; system with RAID and CRYPTO
Package: grub-pc
Version: 1.98+20100705-1
Severity: normal
More smoke testing; still on the original machine. All software is from
squeeze (now including initramfs-tools 0.97) except
for grup-pc and grub-common. Original bug found in squeeze. Updated system;
grub-pc package changed disk ids. Subsequently
package installed grub to all Hitachi drives. update-grub executed and
found 2.6.32-3-amd64 and 2.6.32-5-amd64 kernel images.
When machine rebooted, grub menu appears normally. The 2.6.32-5-amd64 image
is selected and the following occurs:
Loading Linux 2.6.32-5-amd64 ...
error: cannot read the Linux header
Loading initial ramdisk ...
error: you need to load the kernel first.
Press any key to continue...
After this, the grub menu appears again and the 2.6.32-3-amd64 image is
selected and loads normally.
Previously, i.e. two months ago (see above), I had to load the backup initramfs
image by hand in the grub menu.
C. Cropper
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/md1_crypt / xfs
rw,relatime,attr2,logbsize=256k,sunit=512,swidth=1536,noquota 0 0
/dev/md0 /boot xfs rw,sync,relatime,wsync,attr2,noquota 0 0
/dev/mapper/bbox /bbox xfs rw,relatime,attr2,logbufs=8,noquota 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMBXUW
(hd1) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMNPTW
(hd2) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMVVMW
(hd3) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7HW
(hd4) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7RW
(hd5) /dev/disk/by-id/ata-Hitachi_HDS722020ALA330_JK1174YAHMX7VW
(hd6) /dev/disk/by-id/ieee1394-0030e002e0030182:00043c:
(hd7) /dev/disk/by-id/md-uuid-6023ec61:688f13d8:00a731dc:64f342ff
(hd8) /dev/disk/by-id/md-uuid-a8cd9021:89ac8fa3:00a731dc:64f342ff
(hd9) /dev/sda
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/md1_crypt ro
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64 root=/dev/mapper/md1_crypt ro single
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-amd64' --class debian --class
gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_gpt
insmod part_gpt
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echo'Loading Linux 2.6.32-3-amd64 ...'
linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro
echo'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-3-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-3-amd64 (recovery mode)' --class
debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod
Bug#582342: Godel and inconsistency; never will know...; system with RAID and CRYPTO
The problem with grub and my system abruptly disappeared; for whatever reason it has something to do with the MPTSAS driver, the SATA_NV driver, or the bios on my system. Tinkering with my sata DVD writers vanquished the problem! I would be more confused but I have had experiences like this with computers over the years and have studied Godel's incompleteness theorems and the halting problem. Summary: Two internal DVD writers were connected to SAS phy port 6 and port 7 (I have three dvd writers and six hard drives). Attempted to read a DVD disc. Neither writers read the inserted disc very well (driver complains about bad sectors and other stuff). Attempt to read disc from 1394a connected DVD writer; disc reads flawlessly. Turn off computer. Connected DVD writers to __SATA ports 0 and 1__ on motherboard. Leave hard drives connected to SAS ports 0 through 5. Turn on computer. __Re-enable previously-disabled SATA channel 0/1 in the bios__ and indicate that computer should boot from SAS hard drive 0 and save settings. Reboot. Computer POSTs. Grub menu appears. Select 2.6.32-5-amd64 and voila... the machine boots without a problem. Grub bug # 582342 seems to be no more...!?! Any further questions or comments? Otherwise, I will be bidding adieu. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: grub-pc: system with RAID CRYPTO; system with problem to be deactivated August 2010
Sirs and Dames: The system that has the problem discussed under bug #'s 582177 and 582342 will be deactivated the second week of August 2010. It will not be reactivated until October 2010; it might be cannibalized. Should you want me to do anymore major smoke-tests on this bug, I will gladly do two-to-three more until the computer is deactivated. Please get any tests or instructions to me soon. Regards, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: grub-pc: system with RAID CRYPTO; tested initramfs-tools under bug #582177
More information: Smoke-tested system with most recent version of grub-pc and grub-common from sid (versions 1.98+20100617-1 and 1.98+20100617-1) and all recent updates for Squeeze. Sorry for the delay, I had to backup everything to the moon before I could do this... ;-) During the execution of update-grub an error message was posted with the NEW kernel (2.6.32-5-amd64) with the OLD grub: paraphrased... cannot identify / (is /dev mounted?) After updating OLD grub to version 1.98+20100617-1 and executing update-grub, the above error message disappeared. However, when I booted the machine, I cannot load the NEW kernel (2.6.32-5- amd64) at all... error message: error: you need to load the kernel first Press any key to continue... and the grub menu reappears... ...but now I CAN load the initramfs image for the old kernel (2.6.32-3-amd64) that was the original problem. Repeat: I do NOT need to load the initramfs backup image now. The above acts identically with and without the firewire device attached. I am still using the 0.96.1 version of initramfs-tools. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579326: No Audio CD found
This problem has been fixed in the most recent version found in Squeeze. Thank you, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582409: Backends not detected; flac, ape, others
I have the exact same problem. Attempted to manually modify the config file to no avail. Great app. Thank you for your efforts, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ram... /proc/mdstat
Removing the firewire drive when booting doesn't change anything, right? Correct. What could be worth a try (unless grub devs show up): * try initramfs-tools = 0.95.1 * try removing all devices except one disk from the raid1 array and try booting from the single disk then Uhhh? I use this computer on a daily basis! You are going to have to convince me before I experiment anymore. For trying a new initramfs-tools, I don't think I will be doing that at all. For removing all devices from the raid1 array, see the previous paragraph... I just uploaded initramfs-tools 0.96.1, just upgrade it and give it a shot. Booting from the single disk isn't necessary therefore, that would be just another method to isolate the bug. I loaded and booted after the initramfs-tools 0.96.1. The problem persists; I still have to use the backup image to boot the machine. It has something to do with grub not being able to read the image; at least this is what a random error message indicates before the kernel panic previously posted (under Bug#582177) occurs. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ram... /proc/mdstat
Looks ok. /dev/sda is the device you're booting from? I don't know. The bios is set to boot from SAS disk 0 which is **usually** /dev/sda; however, when my firewire drive is connected, on boot all the drives are shifted one drive letter. /dev/sda = /dev/sdb /dev/sdb = /dev/sdc ... etc What could be worth a try (unless grub devs show up): * try initramfs-tools = 0.95.1 * try removing all devices except one disk from the raid1 array and try booting from the single disk then Uhhh? I use this computer on a daily basis! You are going to have to convince me before I experiment anymore. For trying a new initramfs-tools, I don't think I will be doing that at all. For removing all devices from the raid1 array, see the previous paragraph... C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA
synchronize? I don't understand... I have actually pulled different devices in-and-out of the MD devices, let the MD driver rebuild each MD device and made sure the real sda is disk number 0. It does not seem to change... C. Cropper To the bugreporter: Could you please boot a rescue system / live system and synchronize your md device(s) and retry? This strongly looks like an issue with out-of-sync data to me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ram... /proc/mdstat
Can you please provide output of cat /proc/mdstat of the running linux system? r...@loomis:/# cat /proc/mdstat Personalities : [raid1] [raid6] [raid5] [raid4] md1 : active raid6 sdg4[0] sde4[5](S) sdf4[4] sdb4[3] sdd4[2] sdc4[1] 5851753728 blocks level 6, 256k chunk, algorithm 2 [5/5] [U] md0 : active raid1 sdb2[0] sdd2[2](S) sde2[3](S) sdf2[4](S) sdg2[5](S) sdc2[1] 249792 blocks [2/2] [UU] unused devices: none -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... version downgrade
More information I downgraded the initramfs-tools back to version 93.4 and the problem is STILL PRESENT. Honestly, I don't know what to do... it would seem to be that my setup is tenuous at best and there is probably an instability in the boot process that I do not understand. Please advise... C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582177: initramfs-tools: fails to load ramdisk on boot; ... BOOT DEBUG DATA
On Wednesday, May 19, 2010, you wrote: On Wed, May 19, 2010 at 10:36:10AM -0400, crop...@acm.org wrote: More information I downgraded the initramfs-tools back to version 93.4 and the problem is STILL PRESENT. sure, the initramfs won't be changed without telling so, so to have the effect of the downgrade one needs: update-initramfs -u I actually deleted the broken initramfs image and executed: 1) executed update-initramfs -c -k all 2) executed update-grub Therefore, using the 93.4 version as initrd /initrd.img-2.6.32-3-amd64 -- FAILS but using initrd /initrd.img-2.6.32-3-amd64.bak WORKS (?!? :-/) _ Ok, more data... old school capture (pen and paper!) _ Preparations: 1) Reinstalled most recent initramfs-tools version 2) executed update-initramfs -c -k all 3) executed update-grub _ GRUB menu at boot: linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro debug=vc rootdelay=12 echo Loading initial ramdisk initrd /initrd.img-2.6.32-3-amd64 _ Kernel output (LITERAL DATA, except for ... area below): [1.185516] rtc_cmos 00:0a: setting system clock to 2010-05-19 18:18:27 UTC (1274293107) [1.185628] Waiting 12sec before mounting root device [1.199432] input: AT translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1 [12.992053] List of all partitions: [12.992128] No filesystem could mount root, tried: [12.992221] kernel panic - no syncing: VFS: unable to mount root fs on unknown wn-block(0,0) [12.992287] Pid: 1, comm: swapper Not tainted 2.6.32-3-amd64 #1 [12.992340] Call Trace: [12.992397] [812ed349] ? panic+0x86/0x141 ... ...... ... ...... [12.992880] [81011ba0] ? child_rip+0x0/0x20 ___ Observations and opinions: This output format really has NOT changed in the days we have been messing with this problem. 1) the RAID is NOT starting 2) it never gets to the crypto (not started either) 3) no USB/firewire devices are detected (no evidence of drivers loading) 4) no block devices (Hard disks, CDROMs, etc) are detected (no evidence of drivers loading) ___ Questions: 1) Could this be grub? 2) Could resynchronizing md0 fix this problem? I seem to remember doing something like this and the problem went away in March... :-/ 3) Any other suggestions? Thank you for your time, C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582342: grub-pc: fails to load ramdisk on boot; system with RAID CRYPTO; tested initramfs-tools under bug #582177
Package: grub-pc
Version: 1.98-1
Severity: important
Tags: squeeze
Please see debian bug #582177 for some already-done debuging. The only
__grub__ bug I could find that seemed relevant to this problem was #575076.
Very recent changes to the grub-pc have caused my system to fail to load
ramdisk at boot. I have to boot the system with the backup initrd image. I
have checked with rootdelay=10--no change. The problem originally was
thought to be in the initramfs-tools package. The problems appeared in
mid-February 2010. I am only using the squeeze dataset without items from
experimental or other sources.
My system is different from most in that my / partition is inside a luks crypto
container which is then on a RAID 6 volume. The /boot is on an unencrypted
RAID 1 volume. Each physical disk has a separate bios_grub partition (128k)
and the partition tables are GPT.
As I said before this above setup WORKS and I have a 6TB system where the
boot disk can fail (I tested this) and the system comes back alive. For
whatever reason, recent changes to grub-pc 1) make it not see the hard drives
or any USB devices for that mater, 2) fails to start the RAID devices, and thus
3) the kernel panics during the boot sequence.
Thank you for all your work.
C. Cropper
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/md1_crypt / xfs
rw,relatime,attr2,logbsize=256k,sunit=512,swidth=1536,noquota 0 0
/dev/md0 /boot xfs rw,sync,relatime,wsync,attr2,noquota 0 0
/dev/mapper/bbox /bbox xfs rw,relatime,attr2,logbufs=8,noquota 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
(hd2) /dev/sdc
(hd3) /dev/sdd
(hd4) /dev/sde
(hd5) /dev/sdf
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=0
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
insmod raid
insmod mdraid
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
if loadfont /grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod raid
insmod mdraid
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod raid
insmod mdraid
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
insmod png
if background_image /grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, with Linux 2.6.32-3-amd64 --class debian --class
gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echoLoading Linux 2.6.32-3-amd64 ...
linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro quiet
echoLoading initial ramdisk ...
initrd /initrd.img-2.6.32-3-amd64
}
menuentry Debian GNU/Linux, with Linux 2.6.32-3-amd64 (recovery mode) --class
debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod xfs
set root='(md0)'
search --no-floppy --fs-uuid --set aa3fde3d-abc0-468b-8188-fa3a8d3f9fce
echoLoading Linux 2.6.32-3-amd64 ...
linux /vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro single
echoLoading initial ramdisk ...
initrd /initrd.img-2.6.32-3-amd64
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
*** END /boot/grub/grub.cfg
-- System Information:
Debian Release: squeeze/sid
APT
Bug#582177: initramfs-tools: fails to load ramdisk on boot; system with RAID CRYPTO; udev problems?
Package: initramfs-tools Version: 0.94.4 Severity: important Tags: squeeze Very recent changes to the initramfs-tools have caused my system to fail to load ramdisk at boot. I have to boot the system with the backup initrd image. I have checked with rootdelay=10--no change. The problem does not appear to be related to grub. When I boot the machine and watch the mass of kernel data fly by I get the impression that udev is not working or has somehow changed from mid-February till now (all of these problems first appeared in late Feb/early March of 2010). I am only using the squeeze dataset without items from experimental or other sources. My system is different from most in that my / partition is inside a luks crypto container which is then on a RAID 6 volume. The /boot is on an unencrypted RAID 1 volume. Each physical disk has a separate bios_grub partition (128k) and the partition tables are GPT. As I said before this above setup WORKS and I have a 6TB system where the boot disk can fail (I tested this) and the system comes back alive. For whatever reason, recent changes to initramfs-tools 1) make it not see the hard drives or any USB devices for that mater, 2) fails to start the RAID devices, and thus 3) the kernel panics at about 2secs into the boot sequence. Thank you for all your work. Squeeze really is shaping into a mighty force. C. Cropper -- Package-specific info: -- /proc/cmdline BOOT_IMAGE=/vmlinuz-2.6.32-3-amd64 root=/dev/mapper/md1_crypt ro rootdelay=2 -- /proc/filesystems xfs fuseblk -- lsmod Module Size Used by xt_multiport2267 1 nf_nat_ftp 2047 0 nf_conntrack_ftp5537 1 nf_nat_ftp nf_nat_irc 1366 0 nf_conntrack_irc3347 1 nf_nat_irc ipt_REJECT 1953 4 ipt_ULOG7129 17 xt_limit1782 18 xt_tcpudp 2319 54 xt_state1303 65 ipt_MASQUERADE 1554 1 iptable_nat 4299 1 nf_nat 13372 4 nf_nat_ftp,nf_nat_irc,ipt_MASQUERADE,iptable_nat nf_conntrack_ipv4 9833 68 iptable_nat,nf_nat nf_conntrack 46471 9 nf_nat_ftp,nf_conntrack_ftp,nf_nat_irc,nf_conntrack_irc,xt_state,ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 iptable_filter 2258 1 ip_tables 13899 2 iptable_nat,iptable_filter x_tables 12813 9 xt_multiport,ipt_REJECT,ipt_ULOG,xt_limit,xt_tcpudp,xt_state,ipt_MASQUERADE,iptable_nat,ip_tables ppdev 5030 0 lp 7462 0 parport27938 2 ppdev,lp powernow_k810930 0 cpufreq_userspace 1992 0 cpufreq_conservative 5162 0 cpufreq_powersave902 0 cpufreq_stats 2659 0 binfmt_misc 6431 1 fuse 50110 1 loop 11783 0 snd_hda_codec_realtek 235378 1 snd_hda_intel 19619 2 snd_hda_codec 54212 2 snd_hda_codec_realtek,snd_hda_intel usblp 9571 0 snd_hwdep 5364 1 snd_hda_codec snd_pcm_oss32591 0 snd_mixer_oss 12606 1 snd_pcm_oss snd_pcm60615 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_seq_midi4400 0 snd_rawmidi15483 1 snd_seq_midi snd_seq_midi_event 4628 1 snd_seq_midi snd_seq42801 2 snd_seq_midi,snd_seq_midi_event snd_timer 15502 2 snd_pcm,snd_seq snd_seq_device 4477 3 snd_seq_midi,snd_rawmidi,snd_seq amd64_edac_mod 13630 0 snd46350 15 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device edac_core 29245 4 amd64_edac_mod soundcore 4598 1 snd psmouse49505 0 shpchp 26264 0 i2c_nforce2 5280 0 edac_mce_amd6353 1 amd64_edac_mod i2c_core 15584 1 i2c_nforce2 serio_raw 3752 0 pci_hotplug21171 1 shpchp pcspkr 1699 0 snd_page_alloc 6217 2 snd_hda_intel,snd_pcm container 2389 0 evdev 7336 11 processor 30215 2 powernow_k8 xfs 435388 3 exportfs3170 1 xfs sha256_generic 8692 16 cryptd 5366 0 aes_x86_64 7340 16 aes_generic25714 1 aes_x86_64 cbc 2539 8 dm_crypt 10507 8 dm_mod 53674 17 dm_crypt raid45644388 1 async_raid6_recov 5058 1 raid456 async_pq3479 2 raid456,async_raid6_recov raid6_pq 77179 2 async_raid6_recov,async_pq async_xor 2478 3 raid456,async_raid6_recov,async_pq xor 4380 1 async_xor async_memcpy
Bug#582177: initramfs-tools: fails to load ramdisk on boot; more information
More information. In order to get my system to boot I have to go into the editor in GRUB at boot-time and change the initrd /initrd.img-2.6.32-3-amd64 to initrd /initrd.img-2.6.32-3-amd64.bak IF I copy the initrd.img-2.6.32-3-amd64.bak file to initrd.img-2.6.32-3-amd64 on /boot (and rerun update-grub) the computer will still NOT boot (i.e it still fails to load the ramdisk). Summary: I am wondering if this is a GRUB problem. I still believe it is a initramfs-tools problem because it only happened when the initramfs-tools package was changed. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579326: soundkonverter: No Audio CD found
Package: soundkonverter Version: 0.3.10-2 Severity: important Have three DVD burners (one 1394 and two sata). Soundkonverter will not detect Audio CDs when the File - Add CD Tracks command is selected or via any other method. I think this is a problem with the naming convention of the /dev/ folder under Debian Squeeze in tandem with Soundkonverter. I was trying to test this by hand-coding the /dev/sr0, sr1, etc into the SoundKonverter config file but I do not know the variable names. Either way, under Lenny I could detect and encode CDs using Soundkonverter; now the only way I can get Soundkonverter to even recognize a CD is my the command line soundkonverter --rip /dev/'device'. C. Cropper -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages soundkonverter depends on: ii kdelibs4c2a4:3.5.10.dfsg.1-3 core libraries and binaries for al ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcdparanoia0 3.10.2+debian-9 audio extraction tool for sampling ii libgcc11:4.4.2-9 GCC support library ii libqt3-mt 3:3.3.8b-6Qt GUI Library (Threaded runtime v ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libtag1c2a 1.6.2-1 TagLib Audio Meta-Data Library Versions of packages soundkonverter recommends: ii cdda2wav9:1.1.10-1 Dummy transition package for iceda ii cdparanoia 3.10.2+debian-9 audio extraction tool for sampling ii faad2.7-4freeware Advanced Audio Decoder pl ii ffmpeg 5:0.5.1+svn20100411-0.0 audio/video encoder, streaming ser ii flac1.2.1-2+b1 Free Lossless Audio Codec - comman ii kdemultimedia-k 4:4.3.4-1transparent audio CD access for KD ii mp3gain 1.5.1-3 Lossless mp3 normalizer with stati ii mplayer 1:1.0.rc2svn20100313-0.0 The Ultimate Movie Player For Linu ii mppenc 1.16-1 Musepack lossy audio codec encoder ii speex 1.2~rc1-1The Speex codec command line tools pn timiditynone (no description available) ii vorbis-tools1.2.0-6 several Ogg Vorbis tools ii vorbisgain 0.36-3.1 add Replay Gain volume tags to Ogg ii wavpack 4.60.1-1 an audio codec (lossy and lossless soundkonverter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565525: Problem Disappeared; related to printer drivers
This bug appears to not have been a bug with okular. I changed the printer drivers on the Laser Jet 2100 and the problem went away. I do not know what the issue was. C. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552755: Dovecot; Security update broke system
Package: dovecot-imapd Version: 1:1.0.15-2.3+lenny1 Excuse the terseness of this report; this error occurred back in September 09. System: Debian Lenny stable Using postfix and dovecot to serve imap and imaps email; also use squirrelmail. I updated the system (that was working perfectly for months prior) to the security update of dovecot-common and dovecot-imapd. Immediately, all email functions ceased to work. I quickly pulled back to the older version (dovecot-imapd 1:1.0.15-2.3) and did not generate a formal bug report because I panicked; I have businesses that depend on there email. The best I could tell at the time was that the problem had something to do with the private/auth mechanism of postfix interacting with dovecot. The system works perfectly with the held-back version. Sincerely, C. A. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513192: Recoll; Lenny
I will participate; it would ease my participation in this process if you can make the builds debian packages so that I can download and install them easily. I am not keen on compiling AND testing the software (I have my regular life I need to tend to); someone else will need to build the software (with debugging symbols) and then I will install it and test. C. Cropper Kartik Mistry writes: On Thu, Jan 29, 2009 at 12:01 AM, Cropper, C. A. crop...@acm.org wrote: Considering that my computer is nearly unusable, if this bug is not grave or at least serious I don't know what is; I am removing recoll from my system. It NEVER finished the initial indexing. It crashes the ENTIRE system. I tried the sid version as well. Sad to hear this. Can you remove recoll and try once again installing it? It need to be reindex if you are using recoll from 'sid'. Hi, Kartik. Hello M. Cropper, I am the developper for Recoll. I am sorry for your trouble with it, it usually performs quite decently from what I hear. I just found out how to subscribe to the debian package tracking for Recoll by the way, and I'll be able to react faster in the future ... Would you be willing to help me solve the problem, or are you too disgusted with the software to even try ? I don't really understand how it crashes your system, I'd need a more precise description of what actually happens. About the indexer's crash, it would be very helpful to compile a version with debugging symbols and get a stack trace. I can help with a step by step description of how to do this if you can spare the time. I'll be out of email reach for the next week, but let me know if you want to pursue this, and I'll get in touch when I come back. Regards, J.F. Dockes -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513192: Recoll; Lenny
Ok, I'm taking the hint... Considering that my computer is nearly unusable, if this bug is not grave or at least serious I don't know what is; I am removing recoll from my system. It NEVER finished the initial indexing. It crashes the ENTIRE system. I tried the sid version as well. C. Cropper Did that initial indexing finished? Let me know. And, I think its certainly not grave issue. I am marking it as important and forwarding bug to upstream too. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513192: Recoll bug
Failed on the same file after moving to the sid version.
C. Cropper
Trace follows...
:4:../utils/execmd.cpp:163:ExecCmd::doexec: ((nil)|0xd620288)
/usr/share/recoll/filters/rclpdf
{/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040029.pdf}
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/html
:4:../internfile/mh_html.cpp:70:textHtmlToDoc: next_document. defcharset before
parsing: [utf-8]
:4:../internfile/mh_html.cpp:82:Html::mkDoc: pass 0
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/plain
:4:../rcldb/rcldb.cpp:857:Db::add: udi
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040029.pdf|] parent []
:4:../rcldb/rcldb.cpp:1074:Db::add: docid 152958 added
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040029.pdf|]
:4:../rcldb/rcldb.cpp:1133:Db::needUpdate: no path:
[Q/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf|]
:4:../internfile/internfile.cpp:140:FileInterner::FileInterner:
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf] mime [(null)]
preview 0
:4:../internfile/internfile.cpp:201:FileInterner::FileInterner: application/pdf
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf]
:4:../internfile/internfile.cpp:506:FileInterner::internfile. ipath []
:4:../utils/execmd.cpp:163:ExecCmd::doexec: ((nil)|0x2bf3c38)
/usr/share/recoll/filters/rclpdf
{/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf}
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/html
:4:../internfile/mh_html.cpp:70:textHtmlToDoc: next_document. defcharset before
parsing: [utf-8]
:4:../internfile/mh_html.cpp:82:Html::mkDoc: pass 0
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/plain
:4:../rcldb/rcldb.cpp:857:Db::add: udi
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf|] parent []
:4:../rcldb/rcldb.cpp:1074:Db::add: docid 152959 added
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040030.pdf|]
:4:../rcldb/rcldb.cpp:1133:Db::needUpdate: no path:
[Q/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040031.pdf|]
:4:../internfile/internfile.cpp:140:FileInterner::FileInterner:
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040031.pdf] mime [(null)]
preview 0
:4:../internfile/internfile.cpp:201:FileInterner::FileInterner: application/pdf
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040031.pdf]
:4:../internfile/internfile.cpp:506:FileInterner::internfile. ipath []
:4:../utils/execmd.cpp:163:ExecCmd::doexec: ((nil)|0x314ead8)
/usr/share/recoll/filters/rclpdf
{/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040031.pdf}
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/html
:4:../internfile/mh_html.cpp:70:textHtmlToDoc: next_document. defcharset before
parsing: [utf-8]
:4:../internfile/mh_html.cpp:82:Html::mkDoc: pass 0
:4:../internfile/internfile.cpp:423:FileInterner::addHandler: next_doc is
text/plain
:4:../rcldb/rcldb.cpp:857:Db::add: udi
[/home/cac/Journals/PMC/PLoS_Comput_Biol/pcbi.0040031.pdf|] parent []
*** glibc detected *** recollindex: double free or corruption (!prev):
0x0e321c90 ***
=== Backtrace: =
/lib/libc.so.6[0x7fd1c8a47948]
/lib/libc.so.6(cfree+0x76)[0x7fd1c8a49a56]
recollindex[0x47032c]
recollindex[0x4591d4]
recollindex[0x42e46f]
recollindex[0x434a7f]
recollindex[0x41ffd2]
recollindex[0x44eb86]
recollindex[0x44eb36]
recollindex[0x44eb36]
recollindex[0x44eb36]
recollindex[0x44f5a8]
recollindex[0x41e7bc]
recollindex[0x41f129]
recollindex[0x40b829]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7fd1c89f21a6]
recollindex(__gxx_personality_v0+0x219)[0x40a259]
=== Memory map:
0040-00493000 r-xp fe:00 1437696
/usr/bin/recollindex
00693000-006a rw-p 00093000 fe:00 1437696
/usr/bin/recollindex
006a-006a1000 rw-p 006a 00:00 0
014cf000-13b7c000 rw-p 014cf000 00:00 0 [heap]
7fd1c000-7fd1c0021000 rw-p 7fd1c000 00:00 0
7fd1c0021000-7fd1c400 ---p 7fd1c0021000 00:00 0
7fd1c7572000-7fd1c7575000 r-xp fe:00 7084
/usr/lib/gconv/UTF-16.so
7fd1c7575000-7fd1c7774000 ---p 3000 fe:00 7084
/usr/lib/gconv/UTF-16.so
7fd1c7774000-7fd1c7776000 rw-p 2000 fe:00 7084
/usr/lib/gconv/UTF-16.so
7fd1c7979000-7fd1c7983000 r-xp fe:00 5154
/lib/libnss_files-2.7.so
7fd1c7983000-7fd1c7b83000 ---p a000 fe:00 5154
/lib/libnss_files-2.7.so
7fd1c7b83000-7fd1c7b85000 rw-p a000 fe:00 5154
/lib/libnss_files-2.7.so
7fd1c7b85000-7fd1c7b8f000 r-xp fe:00 4788
/lib/libnss_nis-2.7.so
7fd1c7b8f000-7fd1c7d8e000 ---p a000 fe:00 4788
/lib/libnss_nis-2.7.so
7fd1c7d8e000-7fd1c7d9 rw-p 9000 fe:00 4788
/lib/libnss_nis-2.7.so
7fd1c7d9-7fd1c7da5000 r-xp fe:00 5011
Bug#513192: Debian Bug - grave; Recoll (1.10.2-1); Lenny
. Cropper -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
