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.
This seems to have gone away by itself (or by being fixed) sometime during March-April:
jani@saegusa:~$ grep -c xkmfile /var/log/Xorg.*
/var/log/Xorg.0.log:3
/var/log/Xorg.0.log.old:3
/var/log/Xorg.1.log:2
/var/log/Xorg.1.log.old:1507
/var/log/Xorg.2.log:2
/var/log/Xorg.2.log.old:2
/var/log/Xorg.3.log:2
/var/log/Xorg.failsafe.log:2
/var/log/Xorg.failsafe.log.old:2
jani@saegusa:~$ LC_ALL=C ls -lh /var/log/Xorg*
-rw-r–r– 1 root root 60K May 2 20:36 /var/log/Xorg.0.log
-rw-r–r– 1 root root 61K May 2 20:36 /var/log/Xorg.0.log.old
-rw-r–r– 1 root root 48K Apr 22 20:02 /var/log/Xorg.1.log
-rw-r–r– 1 root root 210K Mar 13 22:51 /var/log/Xorg.1.log.old
-rw-r–r– 1 root root 35K Jun 6 2011 /var/log/Xorg.2.log
-rw-r–r– 1 root root 33K Jun 6 2011 /var/log/Xorg.2.log.old
-rw-r–r– 1 root root 35K Jun 6 2011 /var/log/Xorg.3.log
-rw-r–r– 1 root root 32K Apr 29 17:22 /var/log/Xorg.failsafe.log
-rw-r–r– 1 root root 32K Apr 29 17:06 /var/log/Xorg.failsafe.log.old
Ah, scratch me off the list too (or rather, I will), can’t believe I didn’t realize this was for 2D. For us with 3D exhibiting this, there’s at least Bug #990639.
This was working for me during testing, but seems to have cropped up somewhere around release time. If I unmaximize all open windows, the left-side trigger works as intended, but at soon as I maximize one window, the launcher no longer appears no matter how hard I hit the left edge. Also, when this happens, Super just makes everything pale as if dash and launcher were opened on top, but they’re not. Doubly also, there is some gesture that makes things work again, but I have yet to pinpoint what exactly it is. (I just had it happen briefly after temporarily disabling autohide, but that alone wasn’t yet it.)
Universal Access in Control Center allows you to select a text size, though only from fixed preset values and not on pixel/point level.
I’ve just hit the Oops (__ticket_spin_lock+0x9/0x30) with apw’s kernel. I’ll attach the syslog from after reboot to this comment. Had been running the apw build since Monday this week (7 days now) without problems.
Just to note here also that I’ve today switched to apw’s build of 3.2.0-23 [1] linked to from bug 922906. I had been running the upstream 3.3 for more than 7 weeks without hitting this (#917668). The GPU lockup I mentioned in #13 also never reoccurred since that one time.
I’ll report back, should #917668 resurface with the kernel I’m currently running.
* [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/922906/comments/11
Ctrl + 0, Ctrl + Plus Sign and Ctrl + Minus Sign are the designated keyboard shortcuts for controlling the zoom. This works on my setup.
Ctrl + Shift + Minus Sign seems to work identically to Ctrl + Minus Sign, but on my setup, Ctrl + Shift + Plus Sign does nothing, whereas Ctrl + Shift + 0 does what, given Minus Sign’s behaviour, I’d expect Ctrl + Shift + Plus Sign to do: it zooms in.
I’m guessing this is keyboard layout dependent. I’m using the Finnish/Swedish keyboard layout, in which the ’0’ key with Shift is the = character. In US keyboard it seems the Plus Sign has its own key, and that key with the Shift pressed becomes =. This is why Chromium thinks that I’m doing the ’zoom in’ combination when in fact I’m doing the ’reset zoom’ combination with shift.
I came across this while looking for a way to reset the zoom back to my custom default via keyboard. I figured if Ctrl+0 is ’reset to normal’, Ctrl+Shift+0 could be ’reset to default’. (I have yet to find such a keyboard shortcut. That’s a separate issue from the one I’m filing here. I’ll have to file a wishlist bug if said shortcut doesn’t exist.)