Steps to reproduce:
1. $ chromium-browser –temp-profile # just to rule out custom configuration
2. Go to youtube.com/html5, opt in to html5
3. Go to http://www.youtube.com/watch_popup?v=-JryxdydOj0&vq=480

What happens:
The tab goes Aw, Snap! and dmesg says ”chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser”.

What I expect to happen:
I haven’t bothered to check how it should behave, but at least it shouldn’t crash.

Additional information:
Seems to happen with both chromium-codecs-ffmpeg and chromium-codecs-ffmpeg-extra (from Medibuntu) alike.

I’m attaching a backtrace. I did my best with it, but I’ll readily admit I have no idea of its value. Please do advise me if I more -dbg packages or something else is needed.

Wind buntu, have you by any chance opted in to YouTube’s HTML5 programme (see the bottom of page at [1])? I’ve found Chromium is all too eager to crash with WebM, which is the video format used in YouTube’s HTML5 experiment.

It’s not limited to WebM though, there are issues with YouTube videos without HTML5 enabled as well.

*[1] http://www.youtube.com/html5

Ahem. It now looks like non-pae + wistron doesn’t work either. But this looks more like a configuration issue on my part, I’ll have to investigate it further. It still doesn’t freeze or anything, it’s just that the wireless doesn’t go online.

Luis, there actually was a BIOS upgrade available from Fujitsu [1], thanks for prompting me to look! I flashed the latest revision S0Z in (it was S0U until now), but unfortunately this didn’t change the behavior at issue here. (There was no mention of the wireless in manufacturer’s changelog either, but those are often incomplete anyway.)

*[1] http://download.ts.fujitsu.com/download/ShowDescription.asp?SoftwareGUID=1968BB6F-7819-4C8C-A488-BAA44C111F7C

Thanks for commenting, Luis. I booted with noexec=off a couple of times with 3.2.0-24-pae, but it didn’t seem to change anything, i.e. the boot still (seemingly) froze when wistron_btns was enabled.

I was unaware of fsam7400 prior to this, so I tried that too, instead of wistron_btns. With fsam7400, the -pae kernel boots fine here even without noexec=off, apart from a ”Waiting for network” , and the wireless network never coming up (can’t bring it up from the desktop either). So here, at least, the noexec=off workaround isn’t needed with fsam7400, though it isn’t much good wrt the wireless either.

To reiterate: the only way currently to have this system boot with the wireless working is to have wistron_btns enabled and to use a non-pae kernel.

I should mention that I’ve upgraded the laptop to Quantal.

I should also mention that Precise’s mainstream installation media refused to boot on the laptop. I believe the message was ”This kernel requires the following features not present on the CPU: pae”. This despite the fact that the -pae kernels, once a system has been installed, *do* boot and work just fine, albeit not with wistron_btns loaded. So currently I’m unsure whether the CPU actually supports pae or not.

If transmitting the private ssh key over to the server is what we want to avoid, would this work:

1. Encrypt the fs with a symmetric key, encrypt the symmetric key with the ssh public key, store the asymmetrically encrypted symmetric key outside the encrypted fs, throw away the unencrypted symmetric key.
2. When logging in (and after establishing a secure link), send the encrypted (symmetric) key to client for decryption, get back an unencrypted key to use for decrypting the fs.

(I’m only beginning to understand modern cryptography, so I may just have made a fool of myself, but what the hey, you live and learn.)

Attaching a patch to fix this.

u1sdtool is also affected, and for me setting files_sync_enabled to True also doesn’t fix this.

jani@ritoru:~/.config/ubuntuone$ u1sdtool –status

Oops, an error ocurred:
org.freedesktop.DBus.Error.UnknownMethod:

Ah, that would be the ”UbuntuOne token for https://ubuntuone.com”. Missed it repeatedly among the dozens of website passwords.

Just for the record, which exact keys should I delete in Seahorse? I’m affected by this after I removed a (misidentified) computer from my U1 account. I tried removing two Desktopcouch keys that were in Seahorse, but that doesn’t seem to have made any difference:

jani@ritoru:~/.config/ubuntuone$ ubuntuone-control-panel-qt
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.platform.tools.linux.IPCError: org.freedesktop.DBus.Error.UnknownMethod:
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: ubuntuone.platform.tools.linux.IPCError: org.freedesktop.DBus.Error.UnknownMethod:
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 391, in errback
self._startRunCallbacks(fail)
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 458, in _startRunCallbacks
self._runCallbacks()
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 545, in _runCallbacks
current.result = callback(current.result, *args, **kw)
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 1095, in gotResult
_inlineCallbacks(r, g, deferred)
— —
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 1037, in _inlineCallbacks
result = result.throwExceptionIntoGenerator(g)
File ”/usr/lib/python2.7/dist-packages/twisted/python/failure.py”, line 382, in throwExceptionIntoGenerator
return g.throw(self.type, self.value, self.tb)
File ”/usr/lib/python2.7/dist-packages/ubuntuone-control-panel/ubuntuone/controlpanel/gui/qt/controlpanel.py”, line 110, in on_credentials_found
info = yield self.backend.account_info()
File ”/usr/lib/python2.7/dist-packages/twisted/internet/defer.py”, line 1039, in _inlineCallbacks
result = g.send(result)
File ”/usr/lib/python2.7/dist-packages/ubuntuone-control-panel/ubuntuone/controlpanel/backend.py”, line 101, in inner
raise e
ubuntu_sso.utils.webclient.common.UnauthorizedError: (u’Host requires authentication’, u’Invalid access token: 8Lcg72j5LHkGLjgXCgR7′)

This happened after about 30 minutes of watching a flash video in fullscreen (using Firefox): the video froze, leaving just the audio playing, and the display no longer responded to user input until I ssh’d in and killed gnome-session for the user (after which LightDM login came up and things worked again).

According to user this freezing has been occurring daily, sometimes multiple times a day, since upgrading to Precise. It never occurred with Lucid.

We’ve yet to try if using 2D desktop or disabling KMS helps.

(Apport wouldn’t send this report without me lying to it that I was referred here by tech support, but I wasn’t.)

Bug #994203 looks similar, but it’s about NV4e whereas this is an NV4c.