[Bug 54419] Re: usb change between 2.6.15-23 and 2.6.15-26 breaks working setup

Is a fix for this bug available? I notice the bug is confirmed. I experience similar symptoms in this scenario: Transferring large files (600MB+) _to_ an external USB2 device. I'm confident this is not a hardware problem because: Transfers of the exact same files in WinXP experience no issue o

[Bug 54621] Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

I should also note: I've been dual-booting WinXP and Unbuntu Desktop 6.06.1 on this same Powerspec 7121 machine for months now. I don't see any hardware problems when I reboot back to these OSes after attempting the Gutsy/7.10 alternate install. Note that I try the altnernate installs now becaus

[Bug 54621] Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!

Fyi: I received what appears to be the similar if not exactly the same symptoms when I attempted to boot a ubuntu-7.10-alternate-i386.iso based cdrom on a Powerspec 7121 ( http://www.powerspec.com/systems/system_specs.phtml?selection=7121 ) box. The boot-from-cdrom process freezes/hangs at the "se

[Bug 122369] Re: ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

CORRECTION: I was under the impression that I could not upgrade to 6.10. Rereading my original notes, it looks like I have yet to either try 6.10 or have not see symptoms under 6.10. Upgrading to 6.10 may help me a lot. I'll look into trying that later. If 6.10 does not experience this problem

[Bug 122369] Re: ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

This is a data-integrity problem--it destorys my data--and is preventing me from upgrading from 6.06.1, which causing all sorts of other problems. After 2 months I have heard of no one asking me about this problem. Is it that bugs are not sorted by order of importance, that data integrity problem

[Bug 122369] Re: ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

I'm not sure if I've mentioned this previously, but past experience has shown that these symptoms are somewhat repeatable/demonstratable on my system. -- ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup) https://bugs.launchpad.net/bugs/122369 You received this bug notifi

[Bug 122369] ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

rdware prior to the Feisty (7.04) install. I install Feisty, these symptoms arise. I back-rev the install to Dapper (and re-load the data from backup) and I experience no symptoms. This bug doesn't take long to duplicate in my system. I have not attempted to duplicate on more than one h

[Bug 122369] Re: ext2/ext3-fs-related, data-access segmentation fault (running rdiff-backup)

This problem happens only on a Feisty 7.04 Dekstop edition. I've compared with Dapper (which I'm now running) and have had no problems. Sorry I didn't state the version of Ubuntu more clearly at the top (I originally had it listed in the "package" section, but launchpad wouldn't let me do that, a

[Bug 79160] Re: Ubuntu Dapper screen saver crashes X server

I wrote: "I have a 7600 GTS" What I should have written: I have an nvidia 6700 GTS video card. (I'm not sure how to determine the driver rev; let me know if you're interested.) Sorry for any confusion. -Matt -- Ubuntu Dapper screen saver crashes X server https://launchpad.net/bugs/79160 --

[Bug 79160] Re: Ubuntu Dapper screen saver crashes X server

Check out this latest forum post: http://ubuntuforums.org/showpost.php?p=2009622&postcount=11 This doesn't seem to narrow a root cause, though; I'd like to know more than just "reload the driver." Here's my speculation: I suspect that newer 3D imaging software/drivers have issues with an nvidia

[Bug 79160] Ubuntu Dapper screen saver crashes X server

Public bug reported: Ubuntu Dapper screen saver crashes X server. Details here: http://ubuntuforums.org/showthread.php?t=250026 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Ubuntu Dapper screen saver crashes X server https://launchpad.net/bugs/79160 -- ubunt

[Bug 66637] Re: After running mkswap, swap space is discarded, system fails to hibernate (invalid swap signature)

Thomas Schwinge wrote: > Perhaps the same issue as this one? > . Thanks Thomas, I started a followup conversation there. With respect to this bug thread: I am also still curious as to why my system seems to require a "resume=" entry in my /bo

[Bug 74522] Re: boot stall after displaying "IBM Trackpoint..."

I am experiencing 3-minute boot-time startups (almost to the second on my Thinkpad T41 2378DHU) to get to the login screen for an 2.6.17.14 kernel (which I built myself from linux kernel source) running in an Edgy environment. This long boot time did not occur when I was running in a Dapper enviro

[Bug 74522] Re: boot stall after displaying "IBM Trackpoint..."

I am experiencing 3-minute boot-time startups (almost to the second on my Thinkpad T41 2378DHU) to get to the login screen for an 2.6.17.14 kernel (which I built myself from linux kernel source) running in an Edgy environment. This long boot time did not occur when I was running in a Dapper enviro

[Bug 74522] Re: boot stall after displaying "IBM Trackpoint..."

My symptoms appear to be more attributable to the kernel config settings (ie, the ".config" values in the kernel-build-from-source procedure) rather than the kernel revision. I built 2.6.18.6 and 2.6.19.1 with very similar .config values to the slow-booting 2.6.17.14 and experienced the same 3-min

[Bug 66637] Re: After running mkswap, swap space is discarded, system fails to hibernate (invalid swap signature)

A clarification as per above: I was under the impression that Edgy ran "standard" with a 2.6.18.1 kernel...but alas, I may have been mistaken. In any case, the kernel revs I report above are correct, but they may or may not have anything to do with Edgy "standard" stuff, for they may be there sim

[Bug 66637] Re: After running mkswap, swap space is discarded, system fails to hibernate (invalid swap signature)

Without a "resume=UUID=<...>" update to my menu.lst file (for grub), none of this worked. (Alas, maybe one could do a "resume=/dev/hdxx" and it would probably work, too.) Note that I can only get this to work for a 2.6.17.14 kernel running in Edgy; the standard 2.6.18.1 edgy kernel panics for bot