[Bug 589910] Re: I cannot mount a NTFS in terminal with sudo and ntfs-3g. The partition is mounted in 8.04 and Windows (XP and Vista), but after upgrade I got error.
same thing and it repeats itself so its filling up my message file -- I cannot mount a NTFS in terminal with sudo and ntfs-3g. The partition is mounted in 8.04 and Windows (XP and Vista), but after upgrade I got error. https://bugs.launchpad.net/bugs/589910 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
[Bug 487185] Re: [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45
same problem -- [g45] On Intel G45 unable to read EDID block in Dmesg after move from G35 to G45 https://bugs.launchpad.net/bugs/487185 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
[Bug 521640] Re: ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly'
As noted by the comments above, this is a bug. It may be a duplicate of https://bugs.launchpad.net/ubuntu/+bug/539959 and https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/441646 -- ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly' https://bugs.launchpad.net/bugs/521640 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 521640] Re: ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly'
BuAmi I created a new bug report with more details. If you are having the same problem. Note it here https://bugs.launchpad.net/ubuntu/+bug/539959 -- ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly' https://bugs.launchpad.net/bugs/521640 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 441646] Re: gnome power manager prevented gdm login
I whole-hardly agree with you so I've done some research to try and find a common thread in what definitely has become a monumental number of bugs, forum posts etc. ... that probably relate to the same underlying problem and please believe me when I say that I appreciate how difficult it is for you Chris to take this on and we don't want to make your difficult job any more difficult that it already is. I hope the history if not my novice suggestions are helpful. As noted in my own bug report, which probably is some sort of duplicate but I can't figure out where, I am getting a warning that it is an power management installation problem. If this warning is inaccurate, then I believe then some natural cross-referencing of these two ideas is appropriate. Please tell me if I'm wrong but I see a common thread among a lot of bugs and I believe I see a solution to many of them. I believe I've figured out a four part solution to this problem which has been going on since 2006. It's understandable that it has not been addressed because it is not a typical problem. The history itself (which is given below) reveals the solution. Actually, the history I give below is incomplete. The more I research this problem, the more threads I find that relate to this issue (e.g., https://answers.launchpad.net/ubuntu/+question/21286). Part I https://bugzilla.gnome.org/show_bug.cgi?id=144473 has a partial fix for gdm which has not been assigned to anyone because the bug is delegated to linux. It should be redelegated back to gdm. Part II The next part of the fix is that the ubuntu warning that your disk space is low is too weak. It should state that if you don't fix the problem before rebooting, you will lose everything. There should be additional warnings about the problem placed in ubuntu documentation. Part III, ubuntu should abandon encryption until a method is found that allows you to recover a encrypted drive when you have a full-disk. At this point, it is my view that an encrypted drive is just do dangerous because you can lose everything if you have full disk. My proposed solutions of course would make some people unhappy but I believe they are more appropriate than what has been going on since 2006, which is basically to endlessly put off solutions to the problem but I'm certainly not trying to tell you how to do your job. I'm sure that you can come up with better ideas that I can. It's just my perception of the problem. Part IV So my final proposed solution has to do with the tracker team. I'm sure we all appreciate the terrific job the tracker teams do in identifying and addressing problem. So why wasn't the problem solved in 2006? It appears the nature of problem and solution has befuddled the tracker team. The problem was difficult to recognize because a typical debug report is not possible because the user can't login. My proposed solution is to suggest that when a problem has been around for over a year that it is assigned to someone who goal is to identify similar problems in forums and other bug reports. If there is a pattern of a lot of similar bugs and/or questions not being dealt with and no one seems to have a constructive solutions, I would suggest that one person be assigned to come up with a workable solution to the more general problem. This approach would actually save time because instead of endlessly putting out small fires, you would identify an important underlying issue that is contributing to user dissatisfaction. It was quite striking to me when reading all this material, to see so many comments by experienced and highly competent progammers trivialize this issue which has clearly affected a sizeable portion of the Ubuntu community without anyone recognizing it's genuine important or realizing that a simple fix is possible. That's because the problem and solution are more about social psychology than they are about programming. You need a tracking process that addresses this issue. Sometimes the solution might be as simply as updating the documentation. For example, there is documentation about how to handle full-disks. However, this doesn't address all the issues raised in the discussions belows (e.g., how to address the problem when one has an encrypted drive). THE HISTORY Many links below including this one are assigned to gnome-bugs #144473 which means its assigned as a more general linuz problem. Unfortunately, the problem has little to do with linux it has to do with Ubuntu gdm. Next, legitimate confirmed high-priority bugs are linked to this black hole as duplicates. If someone brings it up as a new problem its moved to a question (e.g., https://answers.launchpad.net/ubuntu/+question/38900, https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900 ). As you can see below there is a lot of bugs that claim to have been fixed or illigimate because the solution is simply. You just delete some space but apparently that doesn't work
[Bug 441646] Re: gnome power manager prevented gdm login
As noted in my own bug report, which probably is some sort of duplicate but I can't figure out where, I am getting a warning that it is an power management installation problem. If this warning is inaccurate, then I believe then some natural cross-referencing of these two ideas is appropriate. Please tell me if I'm wrong but I see a common thread among a lot of bugs and I believe I see a solution to many of them. I believe I've figured out a four part solution to this problem which has been going on since 2006. It's understandable that it has not been addressed because it is not a typical problem. The history itself (which is given below) reveals the solution. Actually, the history I give below is incomplete. The more I research this problem, the more threads I find that relate to this issue (e.g., https://answers.launchpad.net/ubuntu/+question/21286). Part I https://bugzilla.gnome.org/show_bug.cgi?id=144473 has a partial fix for gdm which has not been assigned to anyone because the bug is delegated to linux. It should be redelegated back to gdm. Part II The next part of the fix is that the ubuntu warning that your disk space is low is too weak. It should state that if you don't fix the problem before rebooting, you will lose everything. There should be additional warnings about the problem placed in ubuntu documentation. Part III, ubuntu should abandon encryption until a method is found that allows you to recover a encrypted drive when you have a full-disk. At this point, it is my view that an encrypted drive is just do dangerous because you can lose everything if you have full disk. My proposed solutions of course would make some people unhappy but I believe they are more appropriate than what has been going on since 2006, which is basically to endlessly put off solutions to the problem but I'm certainly not trying to tell you how to do your job. I'm sure that you can come up with better ideas that I can. It's just my perception of the problem. Part IV So my final proposed solution has to do with the tracker team. I'm sure we all appreciate the terrific job the tracker teams do in identifying and addressing problem. So why wasn't the problem solved in 2006? It appears the nature of problem and solution has befuddled the tracker team. The problem was difficult to recognize because a typical debug report is not possible because the user can't login. My proposed solution is to suggest that when a problem has been around for over a year that it is assigned to someone who goal is to identify similar problems in forums and other bug reports. If there is a pattern of a lot of similar bugs and/or questions not being dealt with and no one seems to have a constructive solutions, I would suggest that one person be assigned to come up with a workable solution to the more general problem. This approach would actually save time because instead of endlessly putting out small fires, you would identify an important underlying issue that is contributing to user dissatisfaction. It was quite striking to me when reading all this material, to see so many comments by experienced and highly competent progammers trivialize this issue which has clearly affected a sizeable portion of the Ubuntu community without anyone recognizing it's genuine important or realizing that a simple fix is possible. That's because the problem and solution are more about social psychology than they are about programming. You need a tracking process that addresses this issue. Sometimes the solution might be as simply as updating the documentation. For example, there is documentation about how to handle full-disks. However, this doesn't address all the issues raised in the discussions belows (e.g., how to address the problem when one has an encrypted drive). THE HISTORY Many links below including this one are assigned to gnome-bugs #144473 which means its assigned as a more general linuz problem. Unfortunately, the problem has little to do with linux it has to do with Ubuntu gdm. Next, legitimate confirmed high-priority bugs are linked to this black hole as duplicates. If someone brings it up as a new problem its moved to a question (e.g., https://answers.launchpad.net/ubuntu/+question/38900, https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900 ). As you can see below there is a lot of bugs that claim to have been fixed or illigimate because the solution is simply. You just delete some space but apparently that doesn't work in all cases. Some short-term solutions have been painted as panaceas but they are not. To make that point crystal clear imagine that you have an encrypted drive solutions involving chaning sudoers, copying your user directory or deleting $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml or .ICEauthority file. These solutions cannot be accomplished with encrypted drives. Other proposed solutions are just silly. For ex
[Bug 35217] Re: Unable to login when disk space is exhausted
I figured out a four part solution to this problem which has been going on since 2006.The history itself (which is given below) reveals the solution. Part I https://bugzilla.gnome.org/show_bug.cgi?id=144473 has a partial fix for gdm which has not been assigned to anyone. Part II The next part of the fix is that the gnome warning that your disk space is low is too weak. It should state that if you don't fix the problem before rebooting, you will lose everything. There should be additional warnings about the problem placed in ubuntu documentation. Part III, ubuntu should abandon encryption until a method is found that allows you to recover a encrypted drive when you have a full-disk. At this point, it is my view that an encrypted drive is just do dangerous if you can lose everything because you have a full disk. My proposed solutions of course would make some people unhappy but I believe they are more appropriate than what has been going on since 2006, which is basically to endlessly put off the solution to the problem. Part IV So my final proposed solution has to do with the tracker team. I'm sure we all appreciate the terrific job the tracker teams do in identifying and addressing problem. So why wasn't the problem solved in 2006? It appears the nature of problem and solution has befuddled the tracker team. The problem was difficult to recognize because a typical debug report is not possible because the user can't login. My proposed solution is to suggest that when a problem has been around for over a year that it is assigned to someone who goal is to identify similar problems in forums and other bug reports. If there is a pattern of a lot of similar bugs and/or questions not being dealt with and no one seems to have a constructive solutions, I would suggest that one person be assigned to come up with a workable solution to the more general problem. This approach would actually save time because instead of endlessly putting out small fires, you would identify an important underlying issue that is contributing to user dissatisfaction. It was quite striking to me when reading all this material, to see so many comments by experienced and highly competent progammers trivialize this issue which has clearly affected a sizeable portion of the Ubuntu community without anyone recognizing it's genuine important or realizing that a simple fix is possible. That's because the problem and solution are more about social psychology than they are about programming. You need a tracking process that addresses this issue. Sometimes the solution might be as simply as updating the documentation. For example, there is documentation about how to handle full-disks. However, this doesn't address all the issues raised in the discussions belows (e.g., how to address the problem when one has an encrypted drive). THE HISTORY Many links below including this one are assigned to gnome-bugs #144473 which means its assigned as a more general linuz problem. Unfortunately, the problem has little to do with linux it has to do with Ubuntu gdm. Next, legitimate confirmed high-priority bugs are linked to this black hole as duplicates. If someone brings it up as a new problem its moved to a question (e.g., https://answers.launchpad.net/ubuntu/+question/38900, https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900 ). As you can see below there is a lot of bugs that claim to have been fixed or illigimate because the solution is simply. You just delete some space but apparently that doesn't work in all cases. Some short-term solutions have been painted as panaceas but they are not. To make that point crystal clear imagine that you have an encrypted drive solutions involving chaning sudoers, copying your user directory or deleting $HOME/.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml or .ICEauthority file. These solutions cannot be accomplished with encrypted drives. Other proposed solutions are just silly. For example, some solutions involve logining in at the command prompt (forgetting that you can't login in at the command prompt). Others have designated the problem as illigimate because it is too vague or the original questionner has stopped responding to questions after several months or years. Some problems given high priority haven't been fixed since 2006 because no one has ever been assigned the problem. FORUM discussions are ignored and then closed. There has been a lot of forum discussions (see below). https://bugs.launchpad.net/ubuntu/+bug/22842 confirmed, importance high unassigned since 2005 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/35217 not fixed since 2006 assigned to fictional gnome-bugs #144473 which means its assigned to a linuz problem which refers it back to gdm https://answers.launchpad.net/ubuntu/+question/38900, https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+
[Bug 22842] Re: Many programs misbehave when running out of disk space / can't login to fix
I would argue the situation is worse because now in Karmic you have encrypted file systems so the solution of deleting files to free space doesn't work because your .trash file is encrypted. -- Many programs misbehave when running out of disk space / can't login to fix https://bugs.launchpad.net/bugs/22842 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 41170] Re: The typical user will not know how to make some free disk space when he cannot log into a graphical desktop
triaged in 2008 and still not fixed. Now the problem is worse because many people are using encrypted files and the existing solutions (e.g., deleting files to make space) no longer work because .trash file will be encrypted so you can delete all the files you want and it will no decrease the size of the disk. This is definitely a big and still as yet unaddressed problem. -- The typical user will not know how to make some free disk space when he cannot log into a graphical desktop https://bugs.launchpad.net/bugs/41170 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 62638] Re: /home full -> can't log in to gnome
The https://blueprints.edge.launchpad.net/ubuntu/+spec/boot-login-with- full-filesystem solution no longer applies because you can't delete what's in your .trash file if you are using the new encrypted file system. Therefore, the solution is out of date because it doesn't work with encrypted file systems. -- /home full -> can't log in to gnome https://bugs.launchpad.net/bugs/62638 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
[Bug 441646] Re: gnome power manager prevented gdm login
Paul Tagliamonte that might work but Ubuntu now has encrypted drives and most . (including .trash) are now encrypted so you can no longer delete the files in your .trash file if you use encryption which is all the more reason why this is an important bug. -- gnome power manager prevented gdm login https://bugs.launchpad.net/bugs/441646 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
[Bug 441646] Re: gnome power manager prevented gdm login
from the Live CD it says its still full. FilesystemSize Used AvailUse% Mounted on /dev/sda5 187G 183G 0 100% /media/disk However, I removed some software with sudo apt-get remove and deleted some mysql backup files because it said that directory was full in the message logs so the size and actual are different but I see that the available is still 0. -- gnome power manager prevented gdm login https://bugs.launchpad.net/bugs/441646 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
[Bug 539959] [NEW] Install problem after system upgrade
Public bug reported: After upgrading to initrd.img-2.6.31-20-generic I received the following message at the login splash. "The configuration defaults for the GNOME Power manager have not been installed correctly. Please contact your computer administrator" If I attempt to login, I'm simply thrown back to the initial login screen. If I attempted to login using GNOME failsafe I received an message stating "ICEauthority file home/myusername/.ICEauthority could not be updated." I cannot give you a proper bug report because I cannot login to the computer. I thought that this might be a problem with disk space. However, the disk utility states I have 3.6 GB of space free after I attempted to free some space. I initially had some free space. Freeing space did not resolve the problem. CPU EP5300, Intel dual core ASUS Essentio initrd.img-2.6.31-20-generic - dpkg-reconfigure gnome-power-manager has no effect; - I was prompted by apt-get to run dpkg --configure -a, which had no effect - reinstalling gnome-power-manager has no effect. I cannot recover my main directory because it is encrypted and I cannot see some files for that reason if I boot from a live cd. I cannot login at the command prompt no. Is the wiki or blueprint for low disk space helpful for resolving this problem? https://wiki.ubuntu.com/HandleNicelyLowDiskSpace?action=show https://blueprints.launchpad.net/ubuntu/+spec/boot-login-with-full- filesystem Below is the history of similar problems. however, I couldn't find an exact match for the same problem that I am having. http://ubuntuforums.org/showthread.php?t=1355880, https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/441646?comments=all, http://ubuntuforums.org/showthread.php?t=1355880, https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/441646, https://answers.launchpad.net/ubuntu/+question/38900, https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/38894 https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/38894 and https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900 https://answers.launchpad.net/ubuntu/+source/compiz/+question/86687 https://bugs.launchpad.net/gdm/+bug/35217 and under https://bugzilla.gnome.org/show_bug.cgi?id=144473 https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/47145 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: gnome login manager power problem to unable upgrade -- Install problem after system upgrade https://bugs.launchpad.net/bugs/539959 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
[Bug 539959] Re: Install problem after system upgrade
** Attachment added: "various log files" http://launchpadlibrarian.net/41067107/various%20log%20files -- Install problem after system upgrade https://bugs.launchpad.net/bugs/539959 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
[Bug 62638] Re: /home full -> can't log in to gnome
I don't believe this bug is fixed because it assumes that deleting or removing files will solve the problem. I tried this fix and I'm simply told that the disk is still full even though the disk usage utility indicates that I now have 3.6 GB of remaining space. Maybe, it's because I have an encrypted disk. I am new to this so I don't know. -- /home full -> can't log in to gnome https://bugs.launchpad.net/bugs/62638 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
[Bug 47145] Re: It's not possible to login through GUI when disk is full
*** This bug is a duplicate of bug 35217 *** https://bugs.launchpad.net/bugs/35217 This is not a duplicate. Rather 35217 does not seem to understand the problem where here it is understood. Perhaps, 35217 should be considered a duplicate of this thread. Clearly, this is an important problem that should be assigned to someone but it won't be with the attitude displayed on 25217. I would note that this issue occurs on Karmic most recent version. If you have encrypted files, then I do not believe there is a way to recover them but I am new and could be wrong about that. In 35217, the issue seems is also different because the proposed solution involves having the ability to login at the prompt which certainly isn't the case with this bug. -- It's not possible to login through GUI when disk is full https://bugs.launchpad.net/bugs/47145 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 521640] Re: ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly'
Obviously, it's a bug they don't want to fix or address. It obviously isn't just a question . The problem only occurs when your disk is full. It only happens after an upgrade and it does not allow you to delete information. As noted in the existing questions about this bug. It is a bug and is cited as such in notes. Thankfully, Chris was unable to delete all of these bug reports (see above). -- ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly' https://bugs.launchpad.net/bugs/521640 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 441646] Re: gnome power manager prevented gdm login
Dear Mantas, I tried your solution. I deleted 4GB of space and tried to reboot. That didn't solve the problem. I should mention that my drive is encrypted so some parts I cannot delete. -- gnome power manager prevented gdm login https://bugs.launchpad.net/bugs/441646 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
[Bug 35217] Re: Unable to login when disk space is exhausted
I should have also noted that Ted Gould's solution doesn't work in 9.10. That is, simply rebooting the computer has no effect. This problem began with the latest upgrade. -- Unable to login when disk space is exhausted https://bugs.launchpad.net/bugs/35217 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 35217] Re: Unable to login when disk space is exhausted
It appears to me this bug is back. That is, the same thing happened to be in Ubuntu 8.10 today -- Unable to login when disk space is exhausted https://bugs.launchpad.net/bugs/35217 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 521640] Re: ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly'
I believe there must be two bugs. Some people are claiming that they can login at the prompt while others state that they cannot. This bug relates to http://ubuntuforums.org/showthread.php?t=1355880, https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/441646?comments=all, http://ubuntuforums.org/showthread.php?t=1355880, https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/441646, https://answers.launchpad.net/ubuntu/+question/38900, https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/38894 All claimed solutions work for people who can login. There doesn't appear to be a solution for people who cannot. ITo summarize what I read, it may be that for those people who cannot login, that this is a problem relating to a full disk. -- ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly' https://bugs.launchpad.net/bugs/521640 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 441646] Re: gnome power manager prevented gdm login
Mantas Zimnickas solution did not work for me. As noted the bug states that one cannot login at all. For one thing, I cannot login at the command prompt. However, I do have a full disk. I have an Asus Eee 701 as well. I do believe that the problem relates to a full disk. -- gnome power manager prevented gdm login https://bugs.launchpad.net/bugs/441646 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
[Bug 521640] Re: ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly'
I fairly certain that this bug is caused by having a full disk. However, the normal solutions for resolving such a problem (e.g., deleting some files) didn't work for me. The advice given at https://answers.launchpad.net/ubuntu/+question/38900 and https://bugs.launchpad.net/ubuntu/+source/bootcd/+bug/38894 and https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900 did not address the problem for me but clearly these are related bugs. -- ubuntu struck on login screen, message: 'the configuration defaults for the gnome power manager has not been installed correctly' https://bugs.launchpad.net/bugs/521640 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 502439] [NEW] vim-rails fails to install on 9.10
Public bug reported: Binary package hint: vim-rails Although a similar bug was fixed for earlier releases of Karmic, the bug has returned for this version. Attempting to install this package you receive the old error message of "Depends: vim-full but it is not installable." ** Affects: vim-rails (Ubuntu) Importance: Undecided Status: New -- vim-rails fails to install on 9.10 https://bugs.launchpad.net/bugs/502439 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
[Bug 241326] Re: Upgrade to vim-rails 0.4
It says the bug is fixed but apparently it's come back for 9.10 -- Upgrade to vim-rails 0.4 https://bugs.launchpad.net/bugs/241326 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
[Bug 456064] Re: vim-rails fails to install due to depending on vim-full, but vim-full no longer exists
Not fixed in 9.10. The bug is still there. -- vim-rails fails to install due to depending on vim-full, but vim-full no longer exists https://bugs.launchpad.net/bugs/456064 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
[Bug 372014] Re: errors in dmesg
still have the issue as well -- errors in dmesg https://bugs.launchpad.net/bugs/372014 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
[Bug 368941] Re: simultaneous ouput ratelimit freakout 0.9.15
I am getting this error today with the latest version of karmic -- simultaneous ouput ratelimit freakout 0.9.15 https://bugs.launchpad.net/bugs/368941 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
[Bug 477169] Re: Wubi/Karmic boot: kernel panic - not synching: VFS
I'm experiencing this problem on linuz-2.6.31-16-generic. -- Wubi/Karmic boot: kernel panic - not synching: VFS https://bugs.launchpad.net/bugs/477169 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
[Bug 241657] Re: Multiple vulnerabilities in Ruby may lead to a denial of service (DoS) condition or allow execution of arbitrary code.
from http://www.ruby-lang.org/en/news/2008/08/23/dos-vulnerability-in- rexml/ There is a DoS vulnerability in the REXML library used by Rails to parse incoming XML requests. A so-called "XML entity explosion" attack technique can be used for remotely bringing down (disabling) any application which parses user-provided XML. Most Rails applications will be vulnerable to this attack. Impact An attacker can cause a denial of service by causing REXML to parse a document containing recursively nested entities such as: ]> &a; Vulnerable versions 1.8 series * 1.8.6-p287 and all prior versions * 1.8.7-p72 and all prior versions 1.9 series * all versions Solution Please download the following monkey patch to fix this problem. * http://www.ruby-lang.org/security/20080823rexml/rexml- expansion-fix.rb> Then fix your application to load rexml-expansion-fix.rb before using REXML. require "rexml-expansion-fix" ... doc = REXML::Document.new(str) ... If you have a Rails application, copy rexml-expansion-fix.rb into a directory on the load path (such as RAILS_ROOT/lib/), and put the following line into config/environment.rb. require "rexml-expansion-fix" If your application is Rails 2.1 or later, you can simply copy rexml- expansion-fix.rb to RAILS_ROOT/config/initializers and it will be required automatically. By default, XML entity expansion limit is 1. You can change it by changing REXML::Document.entity_expansion_limit. e.g. REXML::Document.entity_expansion_limit = 1000 This fix will be made available as a gem and used by future versions of rails, but users should take corrective action immediately. Credit Credit to Luka Treiber and Mitja Kolsek of ACROS Security for disclosing the problem to Ruby and Rails Security Teams. -- Multiple vulnerabilities in Ruby may lead to a denial of service (DoS) condition or allow execution of arbitrary code. https://bugs.launchpad.net/bugs/241657 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
[Bug 255971] Re: multiple new ruby security vulnerabilities
A new vulnerability has been reported. There is a DoS vulnerability in the REXML library used by Rails to parse incoming XML requests. A so-called "XML entity explosion" attack technique can be used for remotely bringing down (disabling) any application which parses user-provided XML. Most Rails applications will be vulnerable to this attack. Impact An attacker can cause a denial of service by causing REXML to parse a document containing recursively nested entities such as: ]> &a; Vulnerable versions 1.8 series * 1.8.6-p287 and all prior versions * 1.8.7-p72 and all prior versions 1.9 series * all versions Solution Please download the following monkey patch to fix this problem. * http://www.ruby-lang.org/security/20080823rexml/rexml- expansion-fix.rb> Then fix your application to load rexml-expansion-fix.rb before using REXML. require "rexml-expansion-fix" ... doc = REXML::Document.new(str) ... If you have a Rails application, copy rexml-expansion-fix.rb into a directory on the load path (such as RAILS_ROOT/lib/), and put the following line into config/environment.rb. require "rexml-expansion-fix" If your application is Rails 2.1 or later, you can simply copy rexml- expansion-fix.rb to RAILS_ROOT/config/initializers and it will be required automatically. By default, XML entity expansion limit is 1. You can change it by changing REXML::Document.entity_expansion_limit. e.g. REXML::Document.entity_expansion_limit = 1000 This fix will be made available as a gem and used by future versions of rails, but users should take corrective action immediately. Credit Credit to Luka Treiber and Mitja Kolsek of ACROS Security for disclosing the problem to Ruby and Rails Security Teams. -- multiple new ruby security vulnerabilities https://bugs.launchpad.net/bugs/255971 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 201799] Re: Confusing mysqld startup failure with apparmor (Hardy)
followed the recommended steps and it didn't work when I type sudo /etc/init.d/mysqld restart sudo: /etc/init.d/mysqld: command not found synpatic says I do have mysql-server-5.0 installed -- Confusing mysqld startup failure with apparmor (Hardy) https://bugs.launchpad.net/bugs/201799 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
[Bug 243459] Re: Failed to inicialise : Avahi mDNS/DNS-SD Daemon avahi-daemon
Same problem for me. I don't understand what is meant by running an id but all users can logon. I did modify firestarter before the problems started. Also, the syslog indicates that Network Manager appears to be trying to find a wireless connection but I don't have one on this computer. I cannot get so much as a screen if I use my direct connection to the internet. However, if I unplug the connection everything seems to work OK except various gmd problems. It seems to me that gmd is failing because of something going on the Network Manager. -- Failed to inicialise : Avahi mDNS/DNS-SD Daemon avahi-daemon https://bugs.launchpad.net/bugs/243459 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
