Re: [Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
So this is presumed fixed in 8.04? On 3/11/08, Leann Ogasawara [EMAIL PROTECTED] wrote: This bug report is being closed because we received no response to the last inquiry for information. Please reopen it if this is still an issue in the current Ubuntu release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again! ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a direct subscriber of the bug. -- Matt Hoy MBHoy.com -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Scott, Fix released where, Gutsy or Hardy? If Hardy, can we backport into Gutsy? On 12/11/07, Scott Kitterman [EMAIL PROTECTED] wrote: Tested again with the new linux-image-2.6.24-1-generic and the battery is now recognized as well as the CPU temp and A/C state. Marking fix released. ** Changed in: linux (Ubuntu) Status: Triaged = Fix Released ** Changed in: linux (Ubuntu) Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) = (unassigned) -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a direct subscriber of the bug. -- Matt Hoy MBHoy.com -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Why remove hardy-kernel-candidate? I thought this was being worked on for Hardy? On 12/5/07, Leann Ogasawara [EMAIL PROTECTED] wrote: ** Tags removed: hardy-kernel-candidate -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a direct subscriber of the bug. -- Matt Hoy MBHoy.com -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
On 12/2/07, Henrik Nilsen Omma [EMAIL PROTECTED] wrote: This will be retargeted towards the Hardy kernel once it is released. I've tagged this as hardy-kernel-candidate so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as Won't Fix as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks! ** Tags added: hardy-kernel-candidate ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Confirmed = Won't Fix Fair enough. Any chance of seeing this in the backports, or available as a manual fix to Gutsy users? Appreciate the fact you're working on it, but seems a shame we'll have to wait until Hardy. -- Matt Hoy TopicalMatt.com -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
On 12/2/07, Henrik Nilsen Omma [EMAIL PROTECTED] wrote: This bug was nominated for Gutsy but does currently not qualify for a 7.10stable release update (SRU) and the nomination is therefore declined. According the the SRU policy, the fix should already be deployed and tested in the current development version before an update to the stable releases will be considered. With 7.10 now released, that policy applies to this bug. See: https://wiki.ubuntu.com/StableReleaseUpdates . The bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). If the state of this bug should change such that it qualifies for the SRU process, please contact the person who originally declined it and ask them to re-evaluate it. To help improve the state of this bug see: https://wiki.ubuntu.com/Bugs/HowToTriage . Good to know this is being worked on for Hardy, but is there any chance of seeing it in the backports before then? -- Matt Hoy TopicalMatt.com -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
Unfortunately the method Alpensepp posted didn't fix the problem for me, with dmesg still showing: [ 161.472000] FAT: Unrecognized mount option usefree or missing value Maybe I need to remove it elsewhere? I'll investigate further. Glad to see we're making progress on this. -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
The problem with Alpensepp's method was the fact that he used sudo so it only affected the root account. You need to do his method, but without sudo. So, to fix this: 1. Run gconf-editor as a user, NOT in sudo 2. Click into sytem storage default_options vfat on the left folder menu 3. Right click the mount_options key on the right and choose Edit Key 4. An Edit Key dialogue will appear. Highlight usefree by clicking it, and hit Remove 5. Click OK and close the gconf-editor 6. Insert the device of your choice. I'll try and conjure up a .sh script or something, give me time -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
OK, put the attached file in /home/USER/.gconf/system/storage/default_options/vfat to fix this. Overwrite on. ** Attachment added: Put this in /home/USER/.gconf/system/storage/default_options/vfat overwriting the current file http://launchpadlibrarian.net/10169796/%25gconf.xml -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
Made a one click .sh script to fix this. All you need to do is download and run. Basically what it does is goes to the directory with the file that needs replacing, moves the current file to the /tmp directory and downloads a replacement from the above reply in it's place. Thus, fixing your system. What you end up with is a fixed system, and a backup of your configuration in /tmp, meaning if it doesn't work you can quickly undo the change (mv /tmp/backup.xml ~/.gconf/system/storage/default_options/vfat/%gconf.xml) and if it did work the backup will be safely removed from your system on shutdown. So, here's my patch. Thanks to Alpensepp for the initial idea, and launchpad for allowing me to upload the replacement file above. I'll set this as Fix Committed or something and hopefully we can get it into gutsy. ** Attachment added: Download and run to fix bug http://launchpadlibrarian.net/10169832/fix.sh -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
I've uploaded a fix to this in my latest comments to this thread. ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) = Matt Hoy (old-pink) Status: Confirmed = Fix Released -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
I've uploaded a fix to this in my latest comments to this thread. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Fix Released = Fix Committed -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Matt Hoy (old-pink) = Ubuntu Kernel Team (ubuntu-kernel-team) -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] Re: iPod won't mount in Gutsy on 2.6.20-16 kernel
Confirmed by numerous people in: http://ubuntuforums.org/showthread.php?p=3582740#post3582740 ** Changed in: linux-source-2.6.20 (Ubuntu) Status: New = Confirmed -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155436] iPod won't mount in Gutsy on 2.6.20-16 kernel
Public bug reported: Binary package hint: linux-source-2.6.20 May also affect other older kernels. Worked fine with this kernel in Feisty, all perfect. Since Gutsy, iPod only mounts in 2.6.22 kernel, which I can't use because it won't recognize my battery. Basically I get a Unable to mount volume MATT'S IPOD dialogue straight after plugging in, which tells me to view dmesg | tail dmesg | tail shows me: [ 269.276000] sda: assuming drive cache: write through [ 269.288000] SCSI device sda: 14651280 2048-byte hdwr sectors (30006 MB) [ 269.292000] sda: Write Protect is off [ 269.292000] sda: Mode Sense: 68 00 00 08 [ 269.292000] sda: assuming drive cache: write through [ 269.292000] sda: sda1 sda2 [ 269.328000] sd 1:0:0:0: Attached scsi removable disk sda [ 269.328000] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 270.808000] FAT: Unrecognized mount option usefree or missing value [ 292.412000] spurious 8259A interrupt: IRQ15. During all this the iPod displays Do not disconnect Ongoing discussion at: http://ubuntuforums.org/showthread.php?t=583697 ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: New ** Tags: gutsy ipod kernel mount ** Description changed: Binary package hint: linux-source-2.6.20 May also affect other older kernels. Worked fine with this kernel in Feisty, all perfect. Since Gutsy, iPod only mounts in 2.6.22 kernel, which I can't use because it won't recognize my battery. - Basically I get a Unable to mount volume MATT'S IPOD dialogue, which - tells me to view dmesg | tail + Basically I get a Unable to mount volume MATT'S IPOD dialogue + straight after plugging in, which tells me to view dmesg | tail dmesg | tail shows me: [ 269.276000] sda: assuming drive cache: write through [ 269.288000] SCSI device sda: 14651280 2048-byte hdwr sectors (30006 MB) [ 269.292000] sda: Write Protect is off [ 269.292000] sda: Mode Sense: 68 00 00 08 [ 269.292000] sda: assuming drive cache: write through [ 269.292000] sda: sda1 sda2 [ 269.328000] sd 1:0:0:0: Attached scsi removable disk sda [ 269.328000] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 270.808000] FAT: Unrecognized mount option usefree or missing value [ 292.412000] spurious 8259A interrupt: IRQ15. + During all this the iPod displays Do not disconnect + Ongoing discussion at: http://ubuntuforums.org/showthread.php?t=583697 ** Tags added: gutsy ipod kernel mount -- iPod won't mount in Gutsy on 2.6.20-16 kernel https://bugs.launchpad.net/bugs/155436 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
I understand gkrellm could work as a workaround, but that's not what I'm after. I want the original icon in the panel, from acpi, with the accurate, interesting diagnostics. Is there any way I can find what aspect of the kernel is at fault here and report back? Or copy something across from the old firmware into the new firmware folder to get it back? To clarify, 2.6.20-16 works. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Disabling acpi did nothing. Still always on AC, according to this. Gutsy release out, no fix, not impressed. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Interesting. What are the downsides of using that? And I suppose I just edit the grub entry to have acpi=off at the end? On 10/17/07, Scott Kitterman [EMAIL PROTECTED] wrote: Although ancient, the gkrellm is still present in Gutsy. With acpi off, it can get battery status correctly (I expect it doens't use HAL). So that's a work around. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a direct subscriber of the bug. -- Matt Hoy MBHoy.com -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Interesting. What are the downsides of using that? And I suppose I just edit the grub entry to have acpi=off at the end? I'll try it in a bit and report back. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Scott Kitterman wrote on 2007-10-11: Re: [Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 Right but installing the feisty-backports version (from Gutsy) in Feisty causes the same problem. Problem is HAL and something else in Gutsy Booting 2.6.20-16-generic gives me a regular, working battery. 2.6.22-14-generic is the problem. It's the kernel. 2 days until Gutsy release, and I'm worried. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitdue L400
Confirmed, exactly the same problem with my Dell Latitude L400. Perfect/outstanding in 7.04, nothing in 7.10. Constantly says running on AC power Would appreciate fix by final release. Subscribing to this bug. Will try reverting to old hal, if possible. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitdue L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
** Summary changed: - A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitdue L400 + A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 ** Tags added: acpi battery gutsy hal -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Should be in: https://launchpad.net/ubuntu/gutsy/+package/hal ? Installing hal and/or hal-info from the Feisty repository (using dpkg -i --force-all), and rebooting, fixes nothing. If anyone on gutsy HAS managed to fix this, somehow, please let us know in a reply/comment to this. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 127773] Re: A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400
Booting 2.6.20-16-generic gives me a regular, working battery. 2.6.22-14-generic is the problem. -- A/C Status, CPU Temp, and Battery no longer recognized as present after upgrade to Gutsy in Dell Latitude L400 https://bugs.launchpad.net/bugs/127773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
Damage to files from previous attempts and incomplete troubleshooting is a weak defence. Think about it, I purged and reinstalled everything you said to reinstall, even X and everything releated, taking an extra step, and your guide overwrote all nessecary files. So there are no old files remaining in the equation, after running your script. I was negative about two parts of advice. One that was old, badly laid out, hard to follow and broke a previously working part of my system, so I felt it was only right to wrn others to avoid the guide, and yours, which although new broke even more of my system, and you had requested feedback. I've never been told by anyone to install, apart from to fix glxinfo, which I fixed myself, without an install. You, nor any of the guides you work with (or steal from) have mentioned reinstalling. Never. Do not lie. I use the whole how to. Both as a whole paste after activating sudo, and when that doesn't work line by line, to see where it goes wrong. And yes, I stated your copy/paste script broke my networking. GUI interface Network Manager is used to configure wireless, the GUI depends on X, you broke X, left me with a terminal, and no working networking to redownload X for reinstallation. Chances are this has happened to many other WiFi users and they're so stuck without a computer you just haven't heard back from them. And you ended asking for feedback again. But if you are provided with any slightly negative feedback, you'll simply deny it's truth, your guide couldn't possibly be at fault, could it? My advice? Don't use the guide. It broke my system beyond use, and it was only by chance I had another computer I could get it back. You may be lucky enough to have wired networking. However, dougfractal doesn't even own the card, he hasn't tested it himself, he's just compiling old guides into forms of his own and when your setup already working really well, just without the extra of direct rendering, I think I'd rather just live with a less than outstanding video performance than risk losing it all. Chances are it'll be in Gutsy anyway. -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
I do not recommend the use of dougfractal's above script. It rendered my system unusable, with Xorg broken, the ati driver package broken and no means of restoring it, with the backups all pointing to the destroyed ati driver. I had to download xserver-xorg-video-all and xserver-xorg-video-ati onto a memory stick from my other computer, purge them on the laptop in terminal then use sudo dpkg -i to reinstate them. Without another computer or a cable connection, and decent knowledge of terminal commands, you will not be able to recover your system, and may be forced to reinstall. Just hold out for an appearance in Gutsy, or use Mepis. -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34590] Re: DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64
http://ubuntuforums.org/showthread.php?p=3047138#post3047138 Could we PLEASE see this in Gutsy? Possibly with the aid of restricted driver management? Or a working guide for feisty? The guides are so outdated it's literally impossible to get anything to even remotely work, we need a good, new walkthrough. -- DRI not Automatically Enabled for ATI Rage Mobility P/M - Mach64 https://bugs.launchpad.net/bugs/34590 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69395] Re: Slow collection scan only completes 44% and crashes after white screening
Fixed in 1.4.4 -- Slow collection scan only completes 44% and crashes after white screening https://launchpad.net/bugs/69395 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69753] Re: Firefox vanishes shortly after opening
Attached bug report: ** Attachment added: Bug Report http://librarian.launchpad.net/4945703/_usr_lib_firefox_firefox-bin.1000.crash -- Firefox vanishes shortly after opening https://launchpad.net/bugs/69753 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69753] Firefox vanishes shortly after opening
Public bug reported: Just opened firefox, didn't click anything else and it vanished, before asking me to compile a bug report. Personally I think it's just a glitch, as it's never happened before, but I thought I'd report it anyway. ** Affects: firefox (Ubuntu) Importance: Undecided Status: Unconfirmed -- Firefox vanishes shortly after opening https://launchpad.net/bugs/69753 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69395] Slow collection scan only completes 44% and crashes after white screening
Public bug reported: Tried to scan 1415 tracks into the collection, froze at 1%, then 3% then jumped to 44% (over a period of about one hour) before white screening and asking me to submit a bug report. Only 640 tracks were added. Using SQLite, as not that many tracks. Worked fine in older Dapper Drake amaroK, only crashing in the Edgy version. (1.4.3) ** Affects: amarok (Ubuntu) Importance: Undecided Status: Unconfirmed -- Slow collection scan only completes 44% and crashes after white screening https://launchpad.net/bugs/69395 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 69395] Re: Slow collection scan only completes 44% and crashes after white screening
Attached is the FULL bug report: ** Attachment added: Bug report (auto generated) http://librarian.launchpad.net/4941124/_usr_lib_amarok_amarokcollectionscanner.1000.crash -- Slow collection scan only completes 44% and crashes after white screening https://launchpad.net/bugs/69395 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 22363] Re: Equaliser reduces sound volume by a lot when activate
It's true, activate the EQ and the volume drops, but boost the preamp and it'll regain it's previous volume, this isn't a bug. Change the settings and change the sound, it's common knowledge. -- Equaliser reduces sound volume by a lot when activate https://launchpad.net/bugs/22363 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63960] Re: Amarok uses 92% of the CPU every minute in Edgy
I also have 100% CPU usage when scanning for files, so the reply above is logical. -- Amarok uses 92% of the CPU every minute in Edgy https://launchpad.net/bugs/63960 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 69395] Re: Slow collection scan only completes 44% and crashes after white screening
Assigned to the creator of amaroK ** Changed in: amarok (Ubuntu) Assignee: (unassigned) = Brandon Holtsclaw -- Slow collection scan only completes 44% and crashes after white screening https://launchpad.net/bugs/69395 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
