hey guys, i'm using Xubuntu 9.1 and i had safari and i wanted to get rid of it. i did some code in terminal and it finally got rid of it...but it got rid of wine as well. i tried going to Add/Remove and installing wine again but it keeps saying "fix Broken Packages first" can anyone help me get this up and install what ever packages got erased? i greatly appreciate it.
have you tried synaptic yet? there should a section that will tell you about your broken packages or it possibly could be a automator prob. if so you can go into your terminal and code: Code: sudo dpkg --configure -a i hope i was able to sovle your problem
Yes, if you took scum101's advice earlier and installed Debian or Fedora, its package manager can likely fix your momentary problem, as Hardball suggests. However, looking at your posts and your running ... Safari on Wine on Linux (?), I suggest your problems run deeper. Your enthusiasm is impressive, but I suggest you may be trying to do too many things at once: things I should never even try. Here's a maxim: Always do what the programmers' anticipated. Here's a long introduction, which I recently taught my granddaughter. Works for anyone. Let's assume you have Windows XP running on ... a Compaq Armada E500 (a computer & OS discarded & given me). Here's what my granddaughter and I did. (BTW, what is your hardware & software?) Example Installation A. It has one USB port. We invested in a Cisco USB to ethernet dongle and connected it to our ISP directly with DHCP. (We avoided exposing the LAN to its undoubted social diseases.) B. We erased all the user's data to make contiguous space for a CD image. C. We logged onto Debian, clicked Getting Debian, clicked Download a small image file, record it to a CD/DVD/USB disk/floppy, and install using the Internet. Then we chose to download a 'Small CD' image for the i386 processor. This began downloading 'debian-503-i386-netinst.iso to the hard disk. (In fact, we first installed 'Jigdo' and chose an appropriate mirror. Berkeley's failed with an error, so we then chose the principal archive. But none of that is necessary.) D. Having the ISO 9660 image of a CD, we unplugged the internet cord, plugged in an external CD writer, and wrote & labeled a CD. (In fact, we first browsed in Debian for the appropriate .iso for our older system, but this isn't usually necessary.) E. We booted the laptop with the CD. It started a GNU/Linux installer in an old colored text screen and asked us several simple questions. I noted what partitions it could create, then created only a swap & the rest. I'm now measuring the size of the directories that fit in the recommended partitions. When the computer stops changing, I'll repartition it, using the recommended partitions (larger than the sizes we need). If your processor can write DVDs, you may wish to create a special partition large enough to store the image of a dual- or double-sided DVD, before copying it to an optical disc. (An image needs contiguous disk space.) F. We removed the USB plug from the CD writer and plugged in the ethernet. Pressing the last button for 'laptop', we let the installer, still in memory, find the Debian archive and write to our disk the rest of the OS. G. We rebooted without the CD into a new world. The only substantial changes we made were to replace the default mail agent and browser with Icedove (Thunderbird) and Iceweasel (Firefox). These have different names because their interface was changed to be consistent with GNOME's. The only system change we made was to add an easy firewall application that allowed us to block all ports but those we needed. Firefox has many security extensions as well. Oh yes, we installed the flowered screen and changed the icons on Firefox to look like kittens before installing many games. Hints Some hints for avoiding problems: 1. Before becoming a hacker, trek the path millions before you have. Choose a very common, older distribution whose bugs have long been fixed. 2. Take the defaults. (The professionals' maxim.) 3. Use only one new OS until you're very familiar with it. If you then want to use a second, return to its site and follow it's recommendations on dual booting. Before installing or removing a package, read all the documentation on the package installer. Anyone can discover surprising things by reading the documentation. Take pencil notes in a notebook. 4. Use a popular, safe browser for the operating system. This means don't use Safari on Wine on Linux. (Use native applications. This means applications built for the OS running them. Safari was not built for Wine, which was itself grafted onto Linux. Also, running Wine exposes you to much of the malware you left behind when switching to Linux.) 5. Linux is built of 'shells' wrapped around a kernel. The programmers expect you to use the outermost shell to change things. They've made it so such changes 'trickle down' toward the kernel. This means use the OOUI, usually KDE or GNOME, to change things. Using the command line may break things. In particular, 'Wine' uses many boxes of files (libraries) that are used by other applications as well. Your 'installer' (the Synaptic one in GNOME, in our case) knows this and will warn you or leave the libraries needed by any other of your applications. So, were you using Debian's installer, you could ask it to please repair broken packages. It would then install some libraries you removed. Or, you could re-install 'Wine' and remove it again using a package installer. This takes us to Hardball's advice. However, I suggest you not use the command line, but move out to the GUI and use its installer (as the programmers' anticipated).
your answer is in here.. http://ubuntuforums.org/showthread.php?t=186672 don't use wine.. it will run malicious windoze malware just as easily as it will run a legit app.. vey often better.. and you will have no way to resolve the non linux hidden processes.. get rid of it and don't install it again. xubuntu isn't great anyway.. it's a small branch which I tested last year and rejected because it has all the usual ubuntu security faults and upstream experimental repository bugs while not having the user base to get any of the problems resolved quickly. first thing I do with any ubuntu based systems is get rid of sudo and make a proper root account.. just about anybody with a little more than average linux knowhow can walk straight into a sudo secured system... they still haven't fixed the plain text install log which lists the user password... and that's globally readable.
