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
Package: alacarte
Version: 0.13.2-3
Followup-For: Bug #645470
The same bug was triggered here with gnome-shell and python 2.7.
I can confirm Fabians solution - it works again when setting pythin2.6
explicitely.
Steve
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
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
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: Loading
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 init
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
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
Package: e17
Followup-For: Bug #619589
Same here...
I wanted to do a fresh install of e17 which was not possible due to to
conflicting dependancies. After just selecting the "e17" package to
install, a bunch of older (0.9.9.49898-1) packages and newer (1.0.0-2)
packages are marked to install. The
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
Package: xserver-xorg
Version: 1:7.1.0-18
Followup-For: Bug #418953
I also have the problem that the Xserver sometimes segfaults at startup
and sometimes works. But there is no "rule" when it works again (like
every second time as for the original reporter). Sometimes I even have
to reboot. Maybe
10 matches
Mail list logo
