Bug#550621: blanks unrecoverably once in a while

2010-03-02 Thread Jussi Myllykoski
Hi, seems like disabling i915.powersave by default (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564807) did the trick. Regards, -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe"

Bug#565160: console garbled after experimental grub-pc boot

2010-01-16 Thread Jussi Myllykoski
Package: grub-pc Version: 1.98~experimental.20100111.1-1 Severity: normal Similarly to Sven, console is blanked until X starts. Using EeePC 901 with Intel's GMA 950. I did notice that custom kernel (2.6.33-rc4) boots without a hitch. One thing that might have an effect is this option: CONFIG_DR

Bug#550621: blanks unrecoverably once in a while

2009-10-14 Thread Jussi Myllykoski
Hi, did some (admittedly not really extensive) testing and based on it, this issue is not present on 2.6.31.4. Regards, -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Troubl

Bug#548863: initscripts: sendsigs fails

2009-10-09 Thread Jussi Myllykoski
I was experiencing the exact same thing and indeed, udev was the culprit. Fixed in 146-5. Cheers, -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Conta

Bug#544025: ifupdown: starts multiple dhclient instances

2009-10-09 Thread Jussi Myllykoski
Hi! I had similar behavior and it turns out udev was the culprit (#549702). Should be fixed in 146-5, check it out. Regards, -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe"

Bug#549317: sed: can't read /etc/inittab: No such file or directory

2009-10-04 Thread Jussi Myllykoski
etc/init/tty*.conf, but I guess it is good enough for most > cases. It certainly looks like to be working, no error message anymore. Cheers, -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "u

Bug#549317: sed: can't read /etc/inittab: No such file or directory

2009-10-02 Thread Jussi Myllykoski
Package: kbd Version: 1.15-4 Severity: normal I get this message on boot: Setting console screen modes sed: can't read /etc/inittab: No such file or directory This is on a system where sysvinit has been replaced with upstart, so if I understand correctly the data that used to be in /e

Bug#549311: udev: specified group 'scanner' unknown (after upgrade)

2009-10-02 Thread Jussi Myllykoski
Package: udev Version: 146-3 Severity: normal After upgrading to 146-3 (from 0.141-2, I pressume), I get this on boot: Starting the hotplug events dispatcher: udevdudev[1248]: specified group 'scanner' unknown I don't know if this is in any way similar to previous cases of unknown gr

Bug#547491: openbox: layer setting overridden by a full screen app

2009-09-20 Thread Jussi Myllykoski
ch to Iceweasel and if I fullscreen the browser, MPlayer is "lost." Also setting PCManFM on top and aswitch to LXTerminal, same thing happens. I'm using LXDE, I reckon it must be something with that then? -- Jussi Myllykoski jussi.myllyko...@gmail.com -- To UNSUBSCRIBE, email to de

Bug#547491: openbox: layer setting overridden by a full screen app

2009-09-20 Thread Jussi Myllykoski
Package: openbox Version: 3.4.7.2-5 Severity: normal If I set some program's layer to "always on top" and switch to some other program that is fullscreen, the program that should be on top is still on bottom. If the offending program is unfullscreened, layer settings work like expected. -- Syste

Bug#547159: readahead-fedora: fails to read early boot files (segmentation fault)

2009-09-17 Thread Jussi Myllykoski
Package: readahead-fedora Version: 1.5.0-4 Severity: normal After upgrading to 2.6.31, early-readahead fails to read early boot files. ... Reading early boot files...Segmentation fault failed! ... Other init scripts don't fail, e.g. later-readahead is successful. syslog shows following message