[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

2018-04-12 Thread wdoekes
For the record, now that I've moved from Artful 17.10 to Bionic 18.04, this bug is not affecting me anymore, but now bug #1724439 is. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()

2018-04-12 Thread wdoekes
I just upgraded to Ubuntu 18.04 with libmutter 3.28.0-2 and ran into this; monitor poweroff/poweron yields a crash of gnome-shell. The good news is that the applications are not killed like they were in 17.10 (with wayland?). But waiting for the ubuntu-bug crash file to get generated isn't a good

[Bug 1724557] Re: gnome-shell crashed with SIGSEGV in meta_logical_monitor_get_scale()

2018-02-05 Thread wdoekes
@3v1n0: I suspect that this changeset -- which should be in 3.26.3 -- does the same: https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in

[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

2018-02-01 Thread wdoekes
By the way, upstream appears to have a fix for this too: https://gitlab.gnome.org/GNOME/mutter/commit/71b4ef5940d16f7d3cb7dca5c224784315803492 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()

2018-02-01 Thread wdoekes
Perhaps this helps? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724557/comments/29 -> https://downloads.osso.nl/libmutter-3.26.2-ubuntu-artful/libmutter_3.26.2-0ubuntu0.1osso1/ Cheers, Walter Doekes OSSO B.V. -- You received this bug notification because you are a member of

[Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off

2018-02-01 Thread wdoekes
Stack trace looks like https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1724557 here too. Guessing this is a duplicate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.

[Bug 1734791] Re: gnome-keyring doesn't start gnome-keyring-ssh services

2017-12-19 Thread wdoekes
I have the same problem, but with gpg-agent, which also reverse-depends on graphical-session-pre.target. Also upgraded from 17.04 (clean install) to 17.10. I'm not sure where when the --user graphical-session-pre.target is supposed to get started (and by whom), but it appears it never does. If I

[Bug 1426307] Re: location is inaccurate

2015-09-02 Thread wdoekes
I've never had GPS location work without the HERE functions enabled. As soon as I disable it (I have to restart for a change to take effect) I get *no* location info whatsoever. (I have waited for weeks to get a GPS lock, to no avail.) The SensorsStatus tool tells me (when HERE is enabled) that I

[Bug 326199] Re: Shift-alt-tab does not change to previous application

2010-01-08 Thread wdoekes
This, however, should be default behavior. I concur. Same issue in Karmic over here. The fix works. I upgraded from fresh Jaunty install, where I believe it used to work out of the box or I think would've searched for this bug earlier. -- Shift-alt-tab does not change to previous application

[Bug 192508] Re: mouse keys turns on randomly

2009-10-20 Thread wdoekes
Over here, with jaunty on the desktop and jaunty on the NX server, this issue hasn't occurred anymore. Unsubscribing. -- mouse keys turns on randomly https://bugs.launchpad.net/bugs/192508 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug

[Bug 192508] Re: mouse keys turns on randomly

2009-03-13 Thread wdoekes
I've had this issue for a while too. Indeed, pressing shift-numlock enables/disables the feature. I don't intentionally press that, and the only time I hit numlock is when the pad is not in number-mode. I do however use NXclient continuously -- not VNC, but a different kind of terminal server