Closed quesada closed 11 years ago
Yeah, I don't think shellshape could possibly cause that.
Also, your .xsession-errors has a lot of TypeError: this.bounds.update is not a function
errors which I can't reproduce (or see how they could be possible). What version of shellshape are you running? Do you have any modifications?
It's the version from gnome.org. I think. I can rm -rf and download again just in case...
http://josequesada.com @quesada
On Sat, Jan 26, 2013 at 8:54 AM, Tim Cuthbertson notifications@github.comwrote:
Yeah, I don't think shellshape could possibly cause that.
Also, your .xsession-errors has a lot of TypeError: this.bounds.update is not a function errors which I can't reproduce (or see how they could be possible). What version of shellshape are you running? Do you have any modifications?
— Reply to this email directly or view it on GitHubhttps://github.com/gfxmonk/shellshape/issues/109#issuecomment-12732393.
Either way, I'd report this issue (the losing input, not the shellshape log errors) to the gnome-shell bugtracker, as I don't believe shellshape could affect this.
On testing for Gnome 3.12 if found the TypeError: this.bounds.update is not a function
again.
The TypeError only showed up on my gnome-shell while disableing shellshape.
(gnome-shell:11851): Gjs-WARNING **: JS ERROR: TypeError: this.bounds.update is not a function
BaseTiledLayout.prototype.layout@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/tiling.js:875
Workspace.prototype.set_layout@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/workspace.js:184
Workspace.prototype._init@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/workspace.js:107
Workspace@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/workspace.js:91
get_workspace@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/extension.js:108
current_workspace@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/extension.js:185
ShellshapeIndicator.prototype._current_workspace@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/indicator.js:184
ShellshapeIndicator.prototype._active_item@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/indicator.js:167
ShellshapeIndicator.prototype._update_indicator@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/indicator.js:179
ShellshapeIndicator.prototype._workspaceChanged@/home/tvn/.local/share/gnome-shell/extensions/shellshape@gfxmonk.net/indicator.js:162
WindowManager<.actionMoveWorkspace@resource:///org/gnome/shell/ui/windowManager.js:1248
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
WindowManager<._showWorkspaceSwitcher@resource:///org/gnome/shell/ui/windowManager.js:1226
wrapper@resource:///org/gnome/gjs/modules/lang.js:169
I cannot say this is shellshape's fault. I'll try running with no extensions, and see if this doesn't happen.
I'm on ubuntu 12.10, and here's my .xsession-errors http://paste.ubuntu.com/1570660/