Bug#656762: gnome-shell: after "something went wrong" no chance to save any data at all
Package: gnome-session Followup-For: Bug #656762 Hi, I just want to say that I'm too experiencing the issue of massive g-s-d crashes with the "fail-whale" showing up every now and then. For that crash window: it seems to be just a stupid application, so a ALT-F4 closes it and you get your desktop back. As a workaround I downgraded libglib2.0 to version 2.30.2-4 and it seems to run pretty stable, though no thorough testing done yet! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624010: udev: system does not boot because of inactivated lvm root device
Marco d'Itri (14.05.2011, 03:36:51): >Can you try replacing the kill loop in init-bottom/udev with just >"udevadm control --exit"? I tried but it didn't help. But according to the initramfs-tools manpage, the scripts in init-bottom are executed last. So why should this help with the timing issue of a script in local-top? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624010: udev: system does not boot because of inactivated lvm root device
Marco d'Itri (26.04.2011, 15:33:00): >Because they cannot be relevant, and anyway your problem happens in the >initramfs. So I first had a look there and enabled debugging. It looked like the lvm2 script didn't find any VG with udev-168-1: == | + /scripts/local-top/mdadm | Begin: Loadingdone. | + [ -e /conf/param.conf ] | + /scripts/local-top/lvm2 | Volume group "vg01" not found | Skipping volume group vg01 | Unable to find LVM volume vg01/lv01 | + [ -e /conf/param.conf ] | + /scripts/local-top/cryptroot | + [ -e /conf/param.conf ] == But when I started the same script on the initramfs console, the VG and LV were found and activated, so I assumed a timing issue. I then added a "sleep 10" before the activation command in the above script and on the next reboot, the system booted again fine - although with this 10 s delay ;-) I am not very familiar with how exactly initrd is working, what starts first, etc. - but somehow the new udev causes a confusion in the right running order or at least timing. Maybe it takes longer to start… or whatever. Is it possible to change this somehow without this additional "sleep"? Steve -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624010: udev: system does not boot because of inactivated lvm root device
Marco d'Itri (25.04.2011, 21:16:05): >Just to be sure, does the boot process stop in the initramfs or is the >root file system (on LVM or not?) mounted? the root fs is on a LVM but the volume group does not get activated, therefore the root fs cannot be mounted. the boot process stops in the initramfs with the message: "Begin: waiting for root file system..." after a few seconds, the initramfs busybox starts, I activate the LVM volume group (vgchange -a y vg01), exit busybox and the boot process continues (with the message "running scripts/local-premount") >Do you happen to have both /run/udev/ and /dev/.udev/ on your system? I do have /dev/.udev but /run was removed with base-files 6.3 again, so I don't have /run/udev. But since /root is not yet mounted on my system, the error must be something else. >> sorry, this didn't work >Then I do not know what is wrong, and since I do not use LVM on my >developmenet system I fear that you will have to sort this out by >yourself. It would be nice if you could give me some hints, where to investigate, e.g. the changes between 167-3 and 168-1. I found out there had been more changes in the init script than the one you pointed out (at least in structure), so I tried to old script with the new udev, but this also didn't work. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624010: udev: system does not boot because of inactivated lvm root device
Marco d'Itri (25.04.2011, 12:40:45): >Maybe this is related to the init script change? Try this: >-udevadm info --cleanup-db >+rm -rf /dev/.udev/failed/ /run/udev/failed/ sorry, this didn't work (I did run "update-initramfs" after modifying the init script) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624010: udev: system does not boot because of inactivated lvm root device
Package: udev Version: 168-1 Severity: critical Tags: sid Justification: breaks the whole system after updating to udev 168-1 the system stops at boot time because of the missing root device. My root is a LVM device which was not activated during the boot process. After manually activiating it, I was able to resume normal boot. I downgraded udev to 167-3 and the boot process worked again as expected, so it seems new udev doesn't activate LVM volume groups correctly. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages udev depends on: ii debconf [debconf-2.0]1.5.38 Debian configuration management sy ii libc62.11.2-13 Embedded GNU C Library: Shared lib ii libselinux1 2.0.98-1SELinux runtime shared libraries ii libudev0 168-1 libudev shared library ii libusb-0.1-4 2:0.1.12-17 userspace USB programming library ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii util-linux 2.17.2-9.1 Miscellaneous system utilities Versions of packages udev recommends: ii pciutils 1:3.1.7-9 Linux PCI Utilities ii usbutils 1:001-1Linux USB utilities udev suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#579008: ocrfeeder: included module 'util' breaks exfalso/quodlibet
Package: ocrfeeder Version: 0.6.6-1 Severity: critical Tags: sid Justification: breaks unrelated software After installing ocrfeeder the included module 'util' is installed for system wide python access. This breaks exfalso/quodlibet, because they try to access their own 'util' module, but get the one of ocrfeeder instead and therefore crash at startup. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ocrfeeder depends on: ii python 2.5.4-9 An interactive high-level object-o ii python-gtk2 2.17.0-2Python bindings for the GTK+ widge ii python-imaging 1.1.7-1+b1 Python Imaging Library ii python-pygoocanvas 0.10.0-2+b1 GooCanvas Python bindings ii python-support 1.0.8 automated rebuilding support for P ocrfeeder recommends no packages. ocrfeeder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
