Google Chrome/Chromium is buggy on Ubuntu 12.10 [closed] - linux

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
For some reason, ever since I installed Ubuntu 12.10 my Chromium doesn't work well, it's buggy concerning Flash and other random stuff. I tried installing Google Chrome (google-chrome-stable) instead of Chromium, also because the version is more recent than Chromium. Some stuff worked better in comparison to Chromium, like Flash, but now Facebook was all buggy and unusable (the site was literally falling apart as I was scrolling).
Is there a way for me to install Google Chrome on Ubuntu 12.10 without it being buggy? Is somebody experiencing a similar problem?

Installing google-chrome-beta from the Synaptic Package Manager worked for me.

Related

My speakers and headphones are not working on ubuntu 13.04 [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I used to work on Ubuntu 12.10 but then suddenly my speakers stopped working, my headphones didn't used to work before and still they are not working, i then upgraded to 13.04 in hope that it may solve my problem, but it was not the case. I have read dozens of websites and suggestion and tried them out, but none worked. As i open my sound configurations the only option available there is "Play sound through Dummy output" and i am unable to change that. Please help me out.
P.S I have my ubuntu dual booted with windows 7. And the speakers and headphones work fine on windows.
You should install alsa drivers from alsa launchpad.. be sure to install the latest version and that too of raring as you are using 13.04. After install try rebooting the laptop. This will make the sound work.

Looking for free Linux OS [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I would want to install a free Linux OS in my laptop. I am not a techie. I am looking for Linux OS which will have inbuilt features for Fn(Function) keys. Please suggest me if you know any particular Linux OS with these features.
This OS have a laptop version. Easy to use, and supports the newest hardwares:
http://www.ubuntu.com/download/desktop
There are so many choices. Ubuntu is the defacto first distro, although I don't really care for it ever since they went to Unity and Gnome 3. I would rather use Mint with Cinnamon.
A good start is to look at something like Linux Watch http://distrowatch.com/ and see what distros sound good to you, then burn the live disk and check it out. If you like it you can then install it.

Why is it taking so long to support hardware accelerated canvas (html) in Linux/Ubuntu? (Firefox/Chromium) [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
The Windows version of Firefox and Chrome have hardware accelerated canvas, how come this hasn't been done yet on Linux/Ubuntu? Is it Google/Mozilla's fault, or NVIDIA/ATI/Intel? What gives?
I can get it working on Chromium though if I do:
chromium-browser --ignore-gpu-blacklist
But that's hardly ideal and probably blacklisted for a reason.
I can't speak for Google and Mozilla, but I've worked for Opera Software, and I know what a pain it is to support OpenGL on Linux. The quality of the Linux video drivers is usually lower than on Windows, and there is more diversity (proprietary vs. open-source drivers). Plus, Linux-specific development efforts can easily get down-prioritized since the platform is less popular on desktop than Windows and MacOS.
I guess Chromium disables hardware acceleration by default for the same reason Opera currently does that: to avoid exposing users to crashes and hangs. You can enable it if you're prepared that it might not be as stable as you'd like. In fact, you'll help the browser developers if you try it and report any issues you encounter.

I can no longer login to MATE with Linux Mint 13 [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Distro: Linux Mint 13 MATE 32-bit. I can no longer login to MATE after installing the Cinnamon package. (Cinnamon is not working, by the way.) MATE is no longer an option in the login window. (I can login to KDE, bit I want to use MATE.) How can I fix this? Also, what file(s) do I have to modify to change the "xclient script"?
I fixed my immediate problem. I installed mate-session-manager from Synaptic Package Manager. I now can choose MATE before I login. But I'd still like to know about the xclient script.

Is it safe to upgrade to OS X Lion for monotouch developers? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I want to upgrade to OS X Lion but I'm afraid it will mess up my development environment for monotouch. Will upgrading be fairly painless?
I didn't have a problem upgrading aside from the fact that I had to upgrade Xcode to the version built for Lion.
If you upgrade and try to build your iPhone project and you get an error saying it can't find ibtool then upgrading Xcode will solve this.
One other thing that I ran into (after upgrading Xcode) is a bug where the iOS simulator could not find the right version of the SDK libs. I'm not sure if this is monotouch related but you can find the bug report here and what I did to get around it.
Update: Ok. It seems like there are more problems than I realized. Here's another example. Debugging the simulator causes MonoDevelop to crash at random points. See link.

Resources