Inxsible wrote:rabcor wrote:What can i do?Search the forums. There are 3 solved threads on the issue.I am having this same problem without a solution. As fun as it is to be snarky, it would be helpful to link to these threads in the future.
krel
https://bbs.archlinux.org/profile.php?id=65414
2013-04-09T02:56:22Z
bdawg wrote:WonderWoofy wrote:You know there is an edit button?Ya what about itWhen adding information edit your post rather than posting a new post.This thread should not have been posted in the first place, actually. Closing, glad you got it solved, next time search and think first before posting.
ngoonee
https://bbs.archlinux.org/profile.php?id=24040
2012-09-25T02:01:25Z
This is in reference to https://bbs.archlinux.org/viewtopic.php?id=146376Since that thread is marked solved and is getting a little moldy, I thought it more appropriate to start a new thread.Today once again, I had the issue, that is, when sudo gets upgraded, it stops working and after a reboot when I try to ssh back into my embedded device I get nothing but the "system is booting up" me
CokaBear wrote:I looked up the problem, figured out that for the process to go by, i needed to create entropy in the computer, i ran cat /dev/sda for a while until the process finally completed in about a minute.
amandus wrote:I solved it I can have quite mode I don´t now where to edit this.Forum Etiquette wrote:Finally, when a solution is found, mark your thread as solved by editing the first post and prepending the tag [SOLVED] to the title in the "Subject" field.Note that you should avoid using [CLOSED], which is instead used by the system to mark a thread which is no longer accessible for new
vinoman wrote:philm wrote:Ok, I found the issue. There is no /dev/dvd or /dev/cd atm. The device is called /dev/sr0 and /dev/sr1 for the next. Will search the net how to get /dev/dvd and so back.ls -l /dev/{cd,dvd,scd,sr}*That's it!
horsemanoffaith wrote:jasonwryan wrote:...if you encounter difficulties, post here with details ofyour setup, what you have tried and exact error messages.I did exactly that....No, you have done exactly not that. I'm glad you got something working, but you say you don't know why gnome didn't work; neither do we, nor will anyone if you don't take the above advice.If you ar
jasonwryan wrote:Jristz wrote:jasonwryan wrote:Never do pacman -Syuf - it will break your system...in this case, wath is the objective of having a funtions that is recommended never use, instead why no only the -Syu --force and not the -Syuf???is more easy to write unintentionally a -Suyf raten than a -Syu --forceYou use the -f (or --force) option with S; ie., on a single package.
Can someone tell me why threads are closed as solved when they are not solved. Sometimes issues in previous Ubuntu versions continue in newer versions. It seems obvious to reply to a matching thread rather than creating multiple threads with the same topic.