Bug#823061: shadybaby1971-✉-Message-on-hold-

Pic please On Saturday, April 30, 2016, Angel wrote: > > > > > > > > > > > * _Just_saw_something_really_hot_that_made_me_wonder... > _What_would_you_like_me_to_wear_tonight?_ > _What's_the_hottest_thing_I_can_do_for_you_when_I_see_you?_ > We'll_even_play_some_games_honey_ >

Bug#296639: kernel-source-2.4.27: Patches for patch

Package: kernel-source-2.4.27 Version: 2.4.27-8 Followup-For: Bug #296639 I have been monitoring kernel.org for any problems caused by the timer override patch that I submitted earlier and that is included in 2.4.27-8.experimental.1 (and Linus's 2.4.30-pre2). Unfortunately, a couple of bugs have

Bug#296207: xserver-xfree86: [Withdrawing] xanalogtv causes hard lock-ups

Package: xserver-xfree86 Version: 4.3.0.dfsg.1-10 Followup-For: Bug #296207 Further investigation has revealed that this problem can be solved by reducing my CPU and memory speed. I am running nforce2 with a Mobile Athlon XP. I had this at 10x193. So I backed it right down and, after much testing

Bug#296639: kernel-source-2.4.27: nforce[23] backport of acpi_skip_timer_override

Package: kernel-source-2.4.27 Version: 2.4.27-8 Severity: normal Tags: patch The 2.6 kernel series has, since 2.6.5, had a fix for an erroneous timer override present in many BIOSes in nforce[23] chipsets. The 2.4 series is missing this, resulting in an XT_PIC timer on systems that have an

Bug#296642: kernel-source-2.4.27: [drm] filp in LOCK_TEST_WITH_RETURN

Package: kernel-source-2.4.27 Version: 2.4.27-8 Severity: normal The fix for CAN-2004-1056 (Fix insufficient locking checks in DRM code) (see #285563) introduced the filp parameter in the LOCK_TEST_WITH_RETURN macro in drmP.h and various i810 and i830 source files in /drivers/char/drm. As is

Bug#296207: xserver-xfree86: Hard lock-up (no ssh) on running xanalogtv screensaver

Package: xserver-xfree86 Version: 4.3.0.dfsg.1-10 Severity: normal When I run the xanalogtv screen hack of the xscreensaver package, I get a hard lock-up of my whole system. It is not even possible to ssh into it from another machine. This happens reliably although the time that elapses before