Public bug reported:
When i try to open the accounts window i get (in .xsession-errors):
GLib-GObject-WARNING **: instance with invalid (NULL) class pointer
GLib-GObject-CRITICAL **: g_signal_connect_data: assertion
`G_TYPE_CHECK_INSTANCE (instance)' failed
GLib-GObject-WARNING **: invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/909291
Title:
Can't open accounts window
To manage notifications about this bug go to:
I can confirm disabling Zeitgeist plugin fixes the issue for me (Saucy
64bit).
Best regards.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1239218
Title:
[regression]
The issue still happens with all extensions disabled! Only de dock and
appindicators extensions are enabled.
Regards.
Gonçalo Marrafa
On Fri, 23 Nov 2018 at 02:20, Daniel van Vugt
wrote:
> bananenkasper, please log your own bug so as to not confuse the
> debugging process here.
>
&
Thanks for your reply. I've followed the step you recommended to submit a
new bug report.
Regards.
Gonçalo Marrafa
On Wed, 21 Nov 2018 at 02:50, Daniel van Vugt
wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like som
Yes, i have been doing that.
Gonçalo Marrafa
On Thu, 22 Nov 2018 at 08:10, Daniel van Vugt
wrote:
> Yes. See comment #5.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804008
>
> Title:
&g
Is there something I can do to help debug the issue?
Gonçalo Marrafa
On Thu, Nov 22, 2018, 07:50 bananenkasper <1804...@bugs.launchpad.net
wrote:
> Nov 22 08:25:52 p50 gnome-shell[2059]: ../../../../gobject/gsignal.c:2641:
> instance '0x55f5449d57c0' has no handler with id '1293204'
&g
Hi. Thanks for your answer.
Is there some other steps i can take to help debug? It's very hard for me
to disable all extensions since i really depend on some of them to make my
desktop at least usable.
Thanks again. Regards.
Gonçalo Marrafa
On Tue, 20 Nov 2018 at 02:20, Daniel van Vugt
wrote
OK, i will try to pin-point the culprit. I will disable the extensions and
try to figure out which is causing the problem.
Thanks again for your help.
Regards.
Gonçalo Marrafa
On Tue, 20 Nov 2018 at 09:50, Daniel van Vugt
wrote:
> We require that you disable gnome-shell extensions j
Public bug reported:
I have a laptop with an external monitor connected to it. When I log in
my setup is to use only the external monitor. If I, then, switch to a
console and try to switch back to my X session or to the GDM login
screen, my logged in session crashes.
ProblemType: Bug
Public bug reported:
All my gnome-shell extensions randomly (apparently) crash. This behavior
began when i upgraded to cosmic.
Here's a excerpt of my logs:
Nov 19 12:57:28 falcon gnome-shell[1640]: Object Meta.WindowActor
(0x55669ffd87a0), has been already deallocated — impossible to access
Public bug reported:
After upgrading to version 3.30.2-1~ubuntu18.10.3, when I resume from
suspend my laptop reboots. It seems to suspend correctly but when i try
to resume it simply reboots. Every time.
After downgrading to 3.30.1-1, everything is fine again.
This happened only with
Public bug reported:
After the update to 3.32.1 gnome-shell crashes frequently. Before, on
3.32.0, I had no crashes and had a stable desktop. Now, I get 3-4
crashes a day, on average.
Here is log snippet on the crash:
Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: GNOME Shell crashed
Just had another crash. Tried to send the report but Apport shows me the
attached message.
** Attachment added: "Apport error"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+attachment/5271168/+files/Screenshot%20from%202019-06-17%2014-08-52.png
--
You received this bug
Just crashed again. Submitted a new bug report.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1832856
Title:
This crash happened right after unlocking the screen saver.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1833098
Title:
gnome-shell crashed with SIGSEGV in
Just had another crash... Crashed the X session completely!
Jun 18 10:53:03 falcon systemd[1]: Starting Message of the Day...
Jun 18 10:53:03 falcon org.gnome.Shell.desktop[29818]: GNOME Shell crashed with
signal 11
Jun 18 10:53:03 falcon org.gnome.Shell.desktop[29818]: == Stack trace for
I can (somewhat) reliably reproduce the issue. It happens after I unlock
the screen and when I try switching desktops right after that. If I wait
a little after unlocking it seems to work fine.
Hope this helps.
--
You received this bug notification because you are a member of Ubuntu
Desktop
As I stated in the OP, I initially talked with the wsmatrix maintainer
and, as he suggested, disabled the extension for a while and the crashes
continued.
I will try disabling the extension once again and following your
directions in #2 to report new crashes.
--
You received this bug
Btw, I forced the report on the latest crash and that report is
available at
https://errors.ubuntu.com/user/e049722ec528a0ea58304d6b1ba3374e27d4ea39c9bf68afdac98ec882abe5298545fe4527c2cce5895b5b3ad6e493e0853330a2881fd4285e4d43d6c5e2dfa3
--
You received this bug notification because you are a
20 matches
Mail list logo
