![]() One destructive PPA deserves to be mentioned in particular: the Oibaf PPA, which contains graphic drivers and graphical rendering software (notably, but not exclusively, for AMD graphics). Or when you're a tester for a particular piece of software (which you should only be doing on a non-essential test computer). Therefore only use a PPA when you really (really!) have no acceptable alternative. By adding a PPA to your sources list, you give the owner of that PPA in principle full power over your system! It might even contain malware.įurthermore, you make yourself dependent on the owner of the external repository, often only one person, who isn't being checked at all. Therefore it may damage the stability, the reliability and even the security of your system. deb installers, is untested and unverified. Software from third-party repositories (like PPA's) and external. Don't experiment on a production machineīe very careful with external repositories (like PPA's) and with external. Never remove any application that's part of the default installation of Ubuntu or Linux Mint Don't enable the software repository "romeo" UKUU, Ubuntu Mainline Kernel Installer and mainline kernel PPA's Elevated danger level (yellow alert): Ubuntuzilla, UKUU and Ubuntu Mainline Kernel Installer High danger level (orange alert): Ubuntu Sources List Generator Severe danger level (red alert!): Ultamatix ![]() Never use installation scripts like Ultamatix, Ubuntu Sources List Generator, Ubuntuzilla, UKUU and Ubuntu Mainline Kernel Installer Don't install a second full-blown file manager Never use cleaning applications like BleachBit (nor defrag apps) Desklets and applets: think before you install Firefox and Chrome add-ons and extensions: don't trust them blindly Be careful with add-ons, extensions, applets and desklets Only use sudo, pkexec and admin:// when absolutely necessary Be restrictive with root authority (administrative permissions) Be very careful with external repositories (like PPA's) and with external. My other machines, none of which I had ever clicked on "desklets" in system-settings, never had this problem, not even once. Purging didn't remove whatever had changed when I first played with the desklets in system-settings, but removing the desklet code from cinnamon seems to have decisively fixed it. The exception would always be an inability to convert a decimal value somwhere around but not equal to 4 to an integer, and somewhere in all the text before it was the word "desklet" which reminded me of exactly when the problem started and what might fix it. When running Cinnamon from cinnamon -replace in terminal, I would get on only those instances where the panel and hot corner were unresponsive references to a line 823 in /usr/share/ cinnamon/ js/ui/layout. js with a blank (empty) file, and deleted /usr/share/ cinnamon/ desklets entirely and the problem has yet to return. ![]() I replaced /usr/share/ cinnamon/ js/ui/desklet. Re-updated to 1.7.4, logged out and back in, and the panel freezes were back. I clicked on it, clicked on "remove this desklet" and it disappeared. Rolling back to version 1.7.1 DID help-and displayed a "system settings" desklet I had never seen before. Purging Cinnamon from a gnome-shell desktop and reinstalling did not help, nor did removing all non-default applets. I wasn't too worried about it-except from then on, the panel would on restarting cinnamon about half the time become unresponsive to the mouse, and the hot corner also disabled. On my main system, I had once tried out of curiosity to enable desklets from system settings, only to have them not display. I am running cinnamon_ 1.7.4+olivia in three systems converted from Ubuntu Raring.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |