As has been pointed out above, these problems are triggered in a variety
of situations. But for me, the most common culprits have been unwanted
scripts running in the background. I've found that running "NoScript
Security Suite" helps immensely. "NoScript Security Suite" can be found
here:
Hi Dave,
I uploaded some screen captures that paint a better picture of what's
going on. Please see the attachments to my above comments.
You suggested that I attempt to ssh into the frozen VM and, if possible,
look at relevant logs. I was able to access my VM when its desktop was
frozen, but
I'm currently having a similar problem (system freeze) when running
Firefox in an Ubuntu 15.04 virtual machine (VM) under KVM/Qemu. That
is, the VM (but not the host) freezes within a few seconds after
visiting certain sites (including Ubuntu.com) using Firefox in the VM.
I'll just add that:
Just to expand on (and repeat some of) the above:
(1) I haven't run into this problem (system freeze when running visiting
certain sites, including Ubuntu.com, using Firefox) when running bare-metal on
my Intel-based laptop or when running bare-metal on my AMD-based desktop;
(2) The above is
unfrozen2.png - This is a screen capture of the 15.04 VM taken a little
after the screen capture depicted in unfrozen1.png. At this point, I
had closed Firefox. Note that my background image changed to black and
the the text is still garbled.
** Attachment added: unfrozen2.png
unfrozen1.png - This is a screen capture of the 15.04 VM taken several
minutes after the initial freeze. After several minutes, the desktop
unfroze. Note that the site (ubuntu.com) had loaded by the time the
desktop had unfrozen. However, although unfrozen, text is garbled.
** Attachment added:
top.png - This is a screen capture of an ssh session taken while the
15.04 desktop was frozen by Firefox. Top is running. Note that a root
process at over 100% cpu usage.
** Attachment added: top.png
frozen.png - This is a screen capture of the 15.04 VM just after the
desktop froze. Note that the site (ubuntu.com) had not fully loaded at
the time of the freeze.
** Attachment added: frozen.png
Hi Dave:
Sure, I'll do my best to provide more info. To be be candid, I'm a
little busy right now, so it may be a few days.
In the meantime, I'll just note that some sites seem to cause Firefox to
freeze the system more quickly than do other sites. For example,
opening only the default start
I was also having this issue. For me, the solution of setting
Keyboard input method system to None ( System Settings - Language
Support - Language tab) offered by dess seems to be fix. Thanks dess!
Still, I want to add a bit more information:
When my keyboard input method system was set to
Cryptsetup is not currently being installed by default in Ubuntu 14.10
(Utopic). To avoid the issue mentioned by Minosone in comment #6,
cryptsetup should be installed by default, in my opinion.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Also affects Ubuntu 14.10 as of the time of this post.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1371274
Title:
Unable to use the widevine plugin with chromium
Status
Works for me (at least for now) after following this link:
https://www.google.com/maps/preview/?force=webgl
Not quite why following the above links cures the issue, but so far, so
good.
Credit goes to darkhole who suggested using the above link in this post:
I'm having the same problem with Firefox 30 in conjunction with Intel
Sandybridge Mobile. As an alternative, Street View works just fine for
me in the 32-bit version (but not the 64-bit version) of Google Earth,
the .deb for which can be found at
http://www.google.com/earth/download/ge/agree.html
This bug also affects newly released linux-headers-3.14.0-031400-generic
(3.14.0-031400.201403310035) from kernel-ppa/mainline.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
Thanks Robert. Not sure if it helps, but I'll just add that the bug
occurs for me when using either an Nvidia GeForce GT610 or AMD Radeon
HD6670 video card. Also, the bug occurs for me when using either the
appropriate open source driver or the appropriate proprietary driver.
Also, I'll just add
This problem still affects me, even after applying updates. As
reported above by ionash, I am able to type (using my physical keyboard)
in my password after I turn on the on-screen keyboard. But without
first turning on the on-screen keyboard, my physical keyboard isn't
recognized.
--
You
This is rather awkward when using a projector.
The problem also persists when connecting the external screen to the
Mini DisplayPort (with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below this worked correctly under
1366x768 --same-as LVDS1
This is rather awkward when using a projector.
The problem also persists when connecting the external screen to the
Mini DisplayPort (with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below
-as LVDS1
This is rather awkward when using a projector.
The problem also persists when connecting the external screen to the
Mini DisplayPort (with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below this worked
DisplayPort (with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below this worked correctly under 12.10, so this is a
regression and not a feature request.
The output of xrandr --prop with both screens connected in large
to the
Mini DisplayPort (with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below this worked correctly under 12.10, so this is a
regression and not a feature request.
The output of xrandr --prop with both screens
(with adapter) instead of to the HDMI.
I did not test with 12.10 by myself, but according to the comment from
Gizmo Chicken below this worked correctly under 12.10, so this is a
regression and not a feature request.
The output of xrandr --prop with both screens connected in large-
desktop
Adding one more comment:
I notice that the importance if the original report was been changed
from High to Wishlist after triage.
Just to reiterate, the ability to mirror the display across two monitors
using a resolution equal to that of the lower resolution of the two
monitors was a feature
Regarding Ubuntu 13.04: I have a similar problem with an AMD Radeon HD
6670 card connected to two monitors. One monitor (connected via DVI) has
resolution 1440x900 (16:10) and the other monitor (connected via HDMI)
has resolution 1360x768 (16:9).
In my case, when using the mirror displays option
Hans,
Nvidia customer support told me that they don't support Xen dom0. So my
solution to this bug was to replace my Nvidia GeForce card with an AMD
Radeon card. Here's some info that I posted elsewhere:
Yep, it's a shame that Nvidia doesn't support Xen dom0 for most of their
cards.
I
26 matches
Mail list logo
