It seems to be a problem with Gstreamer compatability above version 1.1.4. The
patch has already been applied to GNOME 3.10.1 and exists here:
https://mail.gnome.org/archives/commits-list/2013-September/msg06643.html
could this be applied?
--
You received this bug notification because you are a
Public bug reported:
In Firefox version 25, the WebRTC function does not work and, if one
tries to close the browser, the Firefox process will remain active and
consume large amounts of memory and CPU usage.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You rec
Actually. it's reconfirmed; last time the ati module wasn't loading. It
still throws the same error and segfaults. Here is the error log with
Ubuntu packages from the official repositories.
** Changed in: xorg (Ubuntu)
Status: Invalid => New
** Attachment added: "xorg log with official cur
Never mind, the fix for #1232658 has taken care of it.
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1246991
Title:
Xorg cras
Public bug reported:
Xorg segfaults right after loading the radeonSI module and initializing
glamor if I have xserver-xorg-video-radeon installed. To get it working
again I had to use my Ivybridge graphics exclusively and blacklist the
radeon kernel module.
Attached is the Xorg.0.log up until the
The latest build is working fine. None of the extensions I use crash or
malfunction, and no extension errors are being thrown.
--
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/123
On more recent inspection, this bug seems to be all but fixed in the
latest dev-channel build of Saikrishna Arcot's PPA! All previously
broken extensions now work!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu
Well, the Chromium folks have marked the bug as WontFix...
What is to be done from here?
--
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/1232575
Title:
chrome.extension not a
XKit and PDF-JS both crash due to the same bug.
--
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/1232575
Title:
chrome.extension not available when called from extension script
Now I just feel guilty.
if it's any consolation the PDF-JS extension crashed with the same error
too, as well as XKit.
--
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/1236613
T
Public bug reported:
When using certain extensions starting with Chromium 29, Chromium
crashes and gives the following error (or something similar):
44:44:1006/011329:FATAL:console.cc(62)] Check failed: false. (CONTENT_SCRIPT
context for cellaaeoekimmemgdheibaibbaoeefbl) extensions::lastError:46
Public bug reported:
When I hit the close button for the GNOME System Monitor in Oneiric, it
always takes a few seconds to react. The lag is quite noticeable.
** Affects: gnome-system-monitor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
12 matches
Mail list logo
