[Bug 1760227] Re: gnome-shell crashed with SIGSEGV in js::Shape::matches() from js::ShapeHasher::match() from js::detail::HashTable
I haven't seen this bug in 18.04 nor now in 20.04. -- 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/1760227 Title: gnome-shell crashed with SIGSEGV in js::Shape::matches() from js::ShapeHasher::match() from js::detail::HashTable::SetOps, js::SystemAllocPolicy>::match() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760227/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Thank you Daniel, hopefully by sometime next month 20.04.1LTS will be released and I'll upgrade. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Ref bug #1886110, I submitted this because after almost 2yrs this issue is still valid, at least on my Ubuntu 18.04LTS. I'm commenting here because I was asked to on my other report. According to comments made here - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/501, the last one by Marco Trevisan a commit was made a year ago to fix this issue - https://gitlab.gnome.org/GNOME/gnome- shell/-/commit/a9234f7631f2228184d027419cab1350666ffdc1 therefore I'm wondering why it's not been fixed, at least in my case. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886110] [NEW] localhost gnome-shell[11889]: Object Meta.Background (0x56200a7d4d60), has been already deallocated - impossible to access it. This might be caused by the object having been destro
Public bug reported: Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Using Wallpaper Downloader snap V4.0. Each time a wallpaper is changed for a new one the below is written to syslog: localhost gnome-shell[11889]: Object Meta.Background (0x56200a7d4d60), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 2 16:36:29 localhost gnome-shell[11889]: g_object_run_dispose: assertion 'G_IS_OBJECT (object)' failed Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: == Stack trace for context 0x562008afa340 == Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #0 0x562008f9e0e8 i resource:///org/gnome/shell/ui/background.js:718 (0x7f811800f4d8 @ 22) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #1 0x562008f9e060 i resource:///org/gnome/shell/ui/tweener.js:112 (0x7f81183c8e68 @ 37) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #2 0x7ffddbc7e4e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f81183d2b38 @ 54) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #3 0x7ffddbc7e630 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f81183d2bc0 @ 1626) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #4 0x7ffddbc7e6e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f81183d2c48 @ 100) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #5 0x7ffddbc7e770 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f81183d2cd0 @ 10) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #6 0x7ffddbc7e860 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f81183d2230 @ 386) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #7 0x7ffddbc7e910 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f81183cf808 @ 159) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #8 0x7ffddbc7e970 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f81183b5de0 @ 71) Jul 2 16:36:29 localhost org.gnome.Shell.desktop[11889]: #9 0x7ffddbc7ea10 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f81183cf780 @ 15) I've reported this here - https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/501 as well as here - https://launchpad.net/bugs/1787822 this has never been fixed. I reported this same exact bug on 2018-08-19. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1886110 Title: localhost gnome-shell[11889]: Object Meta.Background (0x56200a7d4d60), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789428] Re: When expunging Evolution trash folder lots of output to syslog such as the below
Thanks Andre for now I'll just do the work around which is to expunge, CTRL-E, within the folder I've deleted the messages from instead of doing it from the trash folder. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1789428 Title: When expunging Evolution trash folder lots of output to syslog such as the below To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1789428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Will do Daniel. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Additional note. When I maximize then minimize the WallPaperDownloader snap this is written to syslog Aug 31 17:05:23 localhost org.gnome.Shell.desktop[2638]: Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Aug 31 17:05:23 localhost org.gnome.Shell.desktop[2638]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x264 (WallpaperD) Aug 31 17:08:35 localhost org.gnome.Shell.desktop[2638]: Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp Aug 31 17:08:35 localhost org.gnome.Shell.desktop[2638]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x264 (WallpaperD) -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog
Done, even blew out the connectors. Don't have another cable at the moment. As far as I can tell it's only Evo that causes this. There are only 3 that I use almost constantly. Ubuntu Firefox, Evo and Xfe file manager. Of those 3 only Evo causes this. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1788739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog
Also note it doesn't just happen when starting Evolution: Aug 30 06:15:34 localhost /usr/lib/gdm3/gdm-x-session[2247]: (II) modeset(0): EDID vendor "ACR", prod id 22 Aug 30 06:17:18 localhost /usr/lib/gdm3/gdm-x-session[2247]: (II) modeset(0): EDID vendor "ACR", prod id 22 Aug 30 07:14:30 localhost /usr/lib/gdm3/gdm-x-session[2247]: (II) modeset(0): EDID vendor "ACR", prod id 22 Aug 30 07:22:44 localhost /usr/lib/gdm3/gdm-x-session[2247]: (II) modeset(0): EDID vendor "ACR", prod id 22 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1788739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog
As far as I can tell Evolution is the only cause of those I usually have running. Output of xrandr: Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192 VGA-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm 1680x1050 59.88*+ 1600x1200 60.00 1280x1024 75.0260.02 1440x900 74.9859.89 1280x960 60.00 1152x864 75.00 1280x720 60.00 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6759.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) ** Attachment added: "output of journalctl -b" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1788739/+attachment/5182627/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1788739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog
** Package changed: rsyslog (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1788739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789428] Re: When expunging Evolution trash folder lots of output to syslog such as the below
Note: When saving this bug report it insisted that it was for Update Manager even though when I started writing it I selected 'Evolution' and the package. I had to go back in manually and change it back to evolution. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1789428 Title: When expunging Evolution trash folder lots of output to syslog such as the below To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1789428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1789428] [NEW] When expunging Evolution trash folder lots of output to syslog such as the below
Public bug reported: Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic apt-cache policy evolution evolution: Installed: 3.28.1-2 Candidate: 3.28.1-2 When expunging just one deleted message from the trash folder this is written to syslog: Aug 28 08:43:04 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:04 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_from: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_subject: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_date_sent: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: message repeated 2 times: [ vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194'] Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_from: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_subject: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_date_sent: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_user_flag: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get orig uid 'AafQOQ342194' Aug 28 08:43:05 localhost evolution[27299]: vee_message_info_get_flags: Failed to get
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
I forgot to mention that I also did a system restart because of a new kernel install so gnome-shell was completely restarted. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
There was a large software update this morning including Gnome-Shell and others. Gnome-Shell was updated to apt-cache policy gnome-shell gnome-shell: Installed: 3.28.3-0ubuntu0.18.04.2 Candidate: 3.28.3-0ubuntu0.18.04.2 Version table: was this supposed to fix the issue I reported above? If so, it didn't. I stopped and restarted the WallPaperDownloader snap: Aug 23 10:43:03 localhost gnome-shell[2506]: Object Meta.Background (0x55b32097d720), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: == Stack trace for context 0x55b31f0c8330 == Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #0 0x55b31f5660f8 i resource:///org/gnome/shell/ui/background.js:718 (0x7f6e1430f450 @ 22) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #1 0x55b31f566070 i resource:///org/gnome/shell/ui/tweener.js:112 (0x7f6e200c8e68 @ 37) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #2 0x7ffd2e233e00 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f6e200d2b38 @ 54) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #3 0x7ffd2e233f50 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f6e200d2bc0 @ 1626) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #4 0x7ffd2e234000 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f6e200d2c48 @ 100) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #5 0x7ffd2e234090 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f6e200d2cd0 @ 10) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #6 0x7ffd2e234180 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6e200d2230 @ 386) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #7 0x7ffd2e234230 b resource:///org/gnome/shell/ui/tweener.js:244 (0x7f6e200cf808 @ 159) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #8 0x7ffd2e234300 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6e200b5de0 @ 71) Aug 23 10:43:03 localhost org.gnome.Shell.desktop[2506]: #9 0x7ffd2e2343a0 b resource:///org/gnome/shell/ui/tweener.js:219 (0x7f6e200cf780 @ 15) -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1788322] [NEW] Approximately every 2mins this is written to syslog - rsyslogd: action 'action 3' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359
Public bug reported: I'm not sure this is a bug but instead is a configuration option missing in the /etc/rsyslog.conf. This is on a Ubuntu 18.04.1LTS system that was upgraded last week from 16.04.5LTS. The version of rsyslog installed is: apt-cache policy rsyslog rsyslog: Installed: 8.32.0-1ubuntu4 Candidate: 8.32.0-1ubuntu4 lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 The complete output is here: https://pastebin.com/AxYYQaw5 I went to the links noted. The first one http://www.rsyslog.com/e/2359 from what I can read tells me that whatever action is referenced it was resumed. I assume in this case it refers to this "resumed (module 'builtin:omfile'" The 2nd link http://www.rsyslog.com/e/2007 seems to give me a fix for this. I've looked for what is mentioned in the 2nd link in my /etc/rsyslog.conf file and in my /etc/rsyslog.d/50- default.conf: The 2nd link refers to this: "A frequent case for this error message on Debian-based distributions (like raspbian) is that rsyslog.conf contains the instruction to write to the xconsole pipe, but this pipe is never read. If so, you can simply delete these lines to remove the error message. These lines are usually found at the end of rsyslog.conf." My current /etc/rsyslog.conf file is here https://pastebin.com/WZVhryNW If I need to add some lines to the .conf file I'm not sure what they should be. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1788322 Title: Approximately every 2mins this is written to syslog - rsyslogd: action 'action 3' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
I'd like to note that I went here - https://bitbucket.org/eloy_garcia_pca/wallpaperdownloader/issues/34/ubuntu-1804 -object-metabackground and opened an issue on the current version of the WallpaperDownloader snap. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Yes, I run a Snap called 'Wallpaperdownloader' that besides downloading wallpapers will also cycle them within a set time limit. I stopped it running at 6:38 this morning and have yet to see the issue resurface. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
On Tue, 2018-08-21 at 01:55 +, Daniel van Vugt wrote: > Thanks. > > Is anything obviously broken or are you just reporting the error > message? > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > No, nothing is obviously broken, at least to me, but something isn't right. However it's an annoyance to have my syslog filled up with these being written every 10 minutes. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 21:23:54 up 8:26, 1 user, load average: 1.35, 1.20, 1.98 Description:Ubuntu 18.04.1 LTS, kernel 4.15.0-32-generic -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
This is: apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 apt-cache policy evolution evolution: Installed: 3.28.1-2 Candidate: 3.28.1-2 lsb_release -crid Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic uname -a Linux localhost 4.15.0-32-generic #35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Aug 20 08:46:13 localhost evolution.desktop[2662]: Memory pressure relief: Total: res = 19537920/16986112/-2551808, res+swap = 14004224/11452416/-2551808 Aug 20 08:46:19 localhost evolution.desktop[2662]: Memory pressure relief: Total: res = 16916480/16908288/-8192, res+swap = 11382784/11374592/-8192 Aug 20 08:46:58 localhost evolution.desktop[2662]: Memory pressure relief: Total: res = 16908288/16908288/0, res+swap = 11374592/11374592/0 Aug 20 08:47:29 localhost evolution.desktop[2662]: Memory pressure relief: Total: res = 16908288/16912384/4096, res+swap = 11378688/11378688/0 Aug 20 08:47:59 localhost evolution.desktop[2662]: Memory pressure relief: Total: res = 16912384/16912384/0, res+swap = 11378688/11378688/0 Not sure if this pertains to this bug at all. I noticed the above every few minutes in my syslog after upgrading to 18.04.1 last week. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Completely removed the extensions in /usr/share/gnome-shell/extensions and restarted. Output still present: Aug 20 06:51:04 localhost gnome-shell[2425]: Object Meta.Background (0x563bb2426370), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: == Stack trace for context 0x563bb076d330 == Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #0 0x563bb0c0cbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7ff39830f450 @ 22) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #1 0x563bb0c0cb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7ff3a40c7e68 @ 37) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #2 0x7ffd0a40b320 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7ff3a40d3b38 @ 54) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #3 0x7ffd0a40b470 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7ff3a40d3bc0 @ 1626) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #4 0x7ffd0a40b520 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7ff3a40d3c48 @ 100) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #5 0x7ffd0a40b5b0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7ff3a40d3cd0 @ 10) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #6 0x7ffd0a40b6a0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7ff3a40d3230 @ 386) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #7 0x7ffd0a40b750 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7ff3a40cf808 @ 159) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #8 0x7ffd0a40b7b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7ff3a40b5de0 @ 71) Aug 20 06:51:05 localhost org.gnome.Shell.desktop[2425]: #9 0x7ffd0a40b850 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7ff3a40cf780 @ 15) Have run journalctl -b > journal.txt and attached output. ** Attachment added: "Output of journalctl -b" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+attachment/5177979/+files/journal.txt -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
apport information ** Tags added: apport-collected bionic ** Description changed: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2014-10-24 (1395 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-32-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-08-17 (3 days ago) + UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177750/+files/Dependencies.txt -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
I reinstalled two of the Gnome Extensions, Freon and Window List since removing all extensions had no effect. -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177751/+files/GsettingsChanges.txt -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1787822/+attachment/5177752/+files/ProcCpuinfoMinimal.txt -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787822] [NEW] gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733335] Re: gnome-shell crashed with SIGABRT in meta_bug()
Crash happened again his afternoon 07/20/2018. Hopefully though when I can upgrade to 18.04.1 this will cease. -- 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/175 Title: gnome-shell crashed with SIGABRT in meta_bug() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/175/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756079] Re: gnome-shell crashed with SIGABRT: "assertion failed: (hlist->tail_before == handler)" in handler_unref_R() from handler_match_free1_R() from signal_handlers_foreach_matched_R() from
Thanks, I'm currently waiting for the release of 18.04.1 LTS to upgrade. -- 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/1756079 Title: gnome-shell crashed with SIGABRT: "assertion failed: (hlist->tail_before == handler)" in handler_unref_R() from handler_match_free1_R() from signal_handlers_foreach_matched_R() from g_signal_handlers_disconnect_matched() from meta_background_actor_set_background() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756079] Re: gnome-shell crashed with SIGABRT: "assertion failed: (hlist->tail_before == handler)" in handler_unref_R() from handler_match_free1_R() from signal_handlers_foreach_matched_R() from
I just opened a bug report on this same problem, 1781060. It's shown as a duplicate of this one however this bug, 1756079 has been in a status of 'New' and 'Unassigned' since I opened it 2018-03-15 -- 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/1756079 Title: gnome-shell crashed with SIGABRT: "assertion failed: (hlist->tail_before == handler)" in handler_unref_R() from handler_match_free1_R() from signal_handlers_foreach_matched_R() from g_signal_handlers_disconnect_matched() from meta_background_actor_set_background() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756079/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
On Fri, 2018-04-27 at 02:15 +, Daniel van Vugt wrote: > I'm guessing the reason why we don't see many reports of this crash > is > because it's possibly triggered by shell extensions that Ubuntu > doesn't > normally ship with. > > Yours are: > b'org.gnome.shell' b'enabled-extensions' b"['freon@UshakovVasilii_Git > hub.yahoo.com', 'netsp...@hedayaty.gmail.com', 'uptime-indicator@gnio > urfgniourf.gmail.com', 'screenshot-window-sizer@gnome-shell-extension > s.gcampax.github.com', 'openweather-extens...@jenslody.de', 'launch-n > ew-insta...@gnome-shell-extensions.gcampax.github.com', 'native-windo > w-placem...@gnome-shell-extensions.gcampax.github.com', 'windowsNavig > a...@gnome-shell-extensions.gcampax.github.com', 'extensions@abteil.o > rg', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'user-the > m...@gnome-shell-extensions.gcampax.github.com', 'places-menu@gnome-she > ll-extensions.gcampax.github.com', 'TaskBar@zpydr', 'drive-menu@gnome > -shell-extensions.gcampax.github.com', 'window-list@gnome-shell-exten > sions.gcampax.github.com']" > > You might want to try disabling extensions to find which, if any, are > causing the crash. > Good idea Daniel I'll give that a try and see how it goes. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 21:24:07 up 4:14, 1 user, load average: 1.25, 1.18, 1.15 Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-39-generic -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref
On Fri, 2018-04-27 at 01:32 +, Daniel van Vugt wrote: > Chris, > > You seem to have opened two bugs for this crash. Bug 1706203 is > almost > the same. > > If it's still happening then let's continue using bug 1706203. > Sounds good to me, I'll just have to remember the next time it happens and 1616651 comes up to actually post any output into 1706203. -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 20:57:55 up 3:48, 1 user, load average: 0.91, 0.79, 0.75 Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-39-generic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() f
Happened again during software update. Hopefully this is fixed in 18.04LTS Syslog output here - https://pastebin.com/yhW3ZSJP -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
The crash happened again when installing the below with sudo apt install: Start-Date: 2018-04-10 16:29:03 Commandline: apt install sqlitebrowser Requested-By: chris (1000) Install: libqt5scintilla2-l10n:amd64 (2.9.1+dfsg-4build1, automatic), libqt5scintilla2-12v5:amd64 (2.9.1+dfsg-4build1, automatic), libqcustomplot1.3:amd64 (1.3.2+dfsg1-1, automatic), sqlitebrowser:amd64 (3.7.0-1) End-Date: 2018-04-10 16:31:25 Syslog output of crash: https://pastebin.com/rna21WiU -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
The crash happened again when installing the below with sudo apt install: Start-Date: 2018-04-10 16:29:03 Commandline: apt install sqlitebrowser Requested-By: chris (1000) Install: libqt5scintilla2-l10n:amd64 (2.9.1+dfsg-4build1, automatic), libqt5scintilla2-12v5:amd64 (2.9.1+dfsg-4build1, automatic), libqcustomplot1.3:amd64 (1.3.2+dfsg1-1, automatic), sqlitebrowser:amd64 (3.7.0-1) End-Date: 2018-04-10 16:31:25 -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()
Thanks Daniel, since I'm sure 18.04 is to be released soon I'll ignore this report. -- 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/1749732 Title: gnome-shell crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()
Happened again however I see a fix has been released for 17.04. Was it also released for 16.04 LTS? Happened when updating: Start-Date: 2018-04-05 17:25:29 Commandline: apt-get -y install firefox firefox-locale-en libruby2.3 ruby2.3 Upgrade: ruby2.3:amd64 (2.3.1-2~16.04.6, 2.3.1-2~16.04.7), libruby2.3:amd64 (2.3.1-2~16.04.6, 2.3.1-2~16.04.7), firefox-locale-en:amd64 (59.0.2+build1-0ubuntu0.16.04.1, 59.0.2+build1-0ubuntu0.16.04.3), firefox:amd64 (59.0.2+build1-0ubuntu0.16.04.1, 59.0.2+build1-0ubuntu0.16.04.3) End-Date: 2018-04-05 17:28:13 Via Webmin 1.881 -- 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/1749732 Title: gnome-shell crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696008] Re: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers()
Gnome Shell crashed again just now while updating Start-Date: 2018-04-02 15:38:42 Commandline: apt dist-upgrade Requested-By: chris (1000) Upgrade: openjdk-8-jre:amd64 (8u151-b12-0ubuntu0.16.04.2, 8u162-b12-0ubuntu0.16.04.2), openjdk-8-jre-headless:amd64 (8u151-b12-0ubuntu0.16.04.2, 8u162-b12-0ubuntu0.16.04.2) End-Date: 2018-04-02 15:43:29 from the command line. This is getting to be an almost constant occurrence, will this be fixed in 18.04? -- 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/1696008 Title: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1696008] Re: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers()
Gnome Shell crashed again this morning while doing software update with Webmin 1.880. apt-cache policy webmin webmin: Installed: 1.880 Candidate: 1.880 lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 uname -a Linux localhost 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- 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/1696008 Title: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1696008/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
Possibly as with comment #10 when an extension was enabled however in my case it happens mostly when updating software or in yesterdays case I installed from Ubuntu Software Center. -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
Not sure what you mean by 'non-standard' extensions. All the extensions I run have been installed from the Gnome extension page. -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
Gnome Shell crashed again while installing a package using Ubuntu Software Center. apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 Here is a paste of the syslog output - https://paste.ubuntu.com/p/Xxv47SGjhH/ -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1755938] Re: gnome-shell crashed with SIGABRT in g_assertion_message()
On Thu, 2018-03-15 at 02:25 +, Daniel van Vugt wrote: > Please do this: > > 1. Apply the workaround from bug 994921. Done, in fact it was already commented out. > 2. Reproduce the crash. Really can't do that as the crash happens very randomly. > 3. Look in /var/crash for new files, and if found run: > ubuntu-bug /var/crash/YOURFILE.crash. Did that. > 4. When the new bug is created, let us know here what that bug ID is. > New bug ID is 1756079 > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 08:23:17 up 20:37, 1 user, load average: 0.79, 0.66, 0.67 Description:Ubuntu 16.04.4 LTS, kernel 4.13.0-37-generic -- 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/1755938 Title: gnome-shell crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1755938] [NEW] gnome-shell crashed with SIGABRT in g_assertion_message()
Public bug reported: lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 Version table: *** 3.18.5-0ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages Happened for no reason that I can see. Syslog output of the crash is here - https://paste.ubuntu.com/p/JJzsS7T6mQ/ ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1755938 Title: gnome-shell crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755938/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733335] Re: gnome-shell crashed with SIGABRT in meta_bug()
Crash happened again this evening for no apparent reason. -- 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/175 Title: gnome-shell crashed with SIGABRT in meta_bug() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/175/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() f
Gnome shell crashed while updating these packages: Start-Date: 2018-02-14 08:14:44 Commandline: apt-get -y install libegl1-mesa libegl1-mesa-dev libgbm-dev libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgles2-mesa libgles2-mesa-dev libosmesa6 libwayland-egl1-mesa libxatracker2 mesa-common-dev mesa-vdpau-drivers Upgrade: libgles2-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libegl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libglapi-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libglapi-mesa:i386 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), mesa-common-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libxatracker2:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libegl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgbm1:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libwayland-egl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgles2-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:i386 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libosmesa6:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libosmesa6:i386 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:i386 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), libgbm-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:amd64 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:i386 (17.2.4-0ubuntu1~16.04.4, 17.2.8-0ubuntu0~16.04.1) End-Date: 2018-02-14 08:19:10 Here is a link to output of /var/log/syslog on PasteBin - https://pastebin.com/q7qsWCKq -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g_object_unref() from desktop_entry_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1616651/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
Crash happened again this morning update of: Commandline: apt-get -y install binutils libpython2.7 libpython2.7-dev libpython2.7-minimal libpython2.7-stdlib python2.7 python2.7-dev python2.7-minimal Upgrade: python2.7-dev:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), python2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), binutils:amd64 (2.26.1-1ubuntu1~16.04.5, 2.26.1-1ubuntu1~16.04.6), libpython2.7:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), python2.7:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), libpython2.7-dev:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3), libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.2, 2.7.12-1ubuntu0~16.04.3) -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***
Happened just now as Firefox was being updated thru software updater. Start-Date: 2017-12-08 16:03:55 Commandline: aptdaemon role='role-commit-packages' sender=':1.124' Upgrade: firefox-mozilla-build:amd64 (57.0.1-0ubuntu1, 57.0.2-0ubuntu1) End-Date: 2017-12-08 16:05:09 -- 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/1705146 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()
That would be great if it happened each and every time I did a software update however the crash is very, very intermittent. -- 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/1706203 Title: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1706203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
I see the same in my Ubuntu 16.04.3 (gnome-shell:3000): GLib-CRITICAL **: Source ID 3572546 was not found when attempting to remove it Kernel 4.10.0-33-generic apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***
I didn't even notice I'd put the release twice. Here's the gnome-shell info: apt-cache policy gnome-shell gnome-shell: Installed: 3.18.5-0ubuntu0.3 Candidate: 3.18.5-0ubuntu0.3 Version table: *** 3.18.5-0ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 100 /var/lib/dpkg/status 3.18.4-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages -- 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/1705146 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***
Thanks, however, I can't access the link you provided. -- 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/1705146 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x05405f00 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
I had to chance this from dconf to tracker. I filed the same bug with Gnome - https://bugzilla.gnome.org/show_bug.cgi?id=779342 and a fix has already been released. ** Package changed: dconf (Ubuntu) => tracker (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1654406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
As you can see this is still happening Feb 23 18:21:40 localhost gnome-settings-daemon.desktop[2991]: (gnome-settings-daemon:2991): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Feb 23 18:21:40 localhost gnome-settings-daemon.desktop[2991]: (gnome-settings-daemon:2991): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
I noticed something this morning that may pertain to this bug report. I'm sure it's been happening for quite awhile but it just happened to catch my eye. Syslog reports: Jan 14 11:38:50 localhost colord[1519]: (colord:1519): Cd-WARNING **: failed to get session [pid 9641]: No such device or address Coincidentally pid 9641 is 9641 root 20 0 94600 8728 6316 S 0.0 0.2 0:00.02 cupsd It also seems that the pid of cupsd changes every six minutes Jan 14 11:32:49 localhost colord[1519]: (colord:1519): Cd-WARNING **: failed to get session [pid 9302]: No such device or address Jan 14 11:38:50 localhost colord[1519]: (colord:1519): Cd-WARNING **: failed to get session [pid 9641]: No such device or address Jan 14 11:45:49 localhost colord[1519]: (colord:1519): Cd-WARNING **: failed to get session [pid 9951]: No such device or address 9951 root 20 0 94604 8660 6244 S 0.0 0.2 0:00.03 cupsd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1654406] Re: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.
** Package changed: d-conf (Ubuntu) => tracker (Ubuntu) ** Package changed: tracker (Ubuntu) => dconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1654406 Title: Ubuntu 16.04.1LTS - (tracker-extract:3459): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
Why is this bug still have a status of new? It's still happening. Version of gnome-settings-daemon I'm using now: chris@localhost:~$ apt-cache policy gnome-settings-daemon gnome-settings-daemon: Installed: 3.20.1-2ubuntu1~ubuntu16.04.1 Candidate: 3.20.1-2ubuntu1~ubuntu16.04.1 Version table: *** 3.20.1-2ubuntu1~ubuntu16.04.1 500 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Jan 3 15:01:54 localhost gnome-settings-daemon.desktop[2527]: (gnome-settings-daemon:2527): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 Jan 3 15:01:54 localhost gnome-settings-daemon.desktop[2527]: (gnome-settings-daemon:2527): color-plugin-WARNING **: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_PDF -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1635715] Re: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020
I forgot to add the package ** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1635715 Title: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_HP_LaserJet_1020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1635715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1613802] Re: When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes
I just reported this to Gnome Bugzilla - https://bugzilla.gnome.org/show_bug.cgi?id=770916 ** Bug watch added: GNOME Bug Tracker #770916 https://bugzilla.gnome.org/show_bug.cgi?id=770916 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1613802 Title: When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1613802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1613802] Re: When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes
Is this being looked at yet? It's still happening every 15 minutes whenever the tablet is connected via USB. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1613802 Title: When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1613802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1613802] [NEW] When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes
Public bug reported: Description: Ubuntu 16.04.1 LTS Release:16.04 gvfs information chris@localhost:~$ apt-cache policy gvfs gvfs: Installed: 1.28.2-1ubuntu1~16.04.1 Candidate: 1.28.2-1ubuntu1~16.04.1 Version table: *** 1.28.2-1ubuntu1~16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.28.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Every 15 minutes when I have my Amazon Fire HDX 8.9 tablet connected via USB to my desktop information on the tablet is being written to my syslog causing it to grow very large. This same issue did NOT occur in 14.04 LTS. I've tried a different USB port and a different USB cable with the same results. Below is what is put into the syslog. What should have happened - if anything just this which is the tablet: Aug 16 10:59:14 localhost kernel: [661846.880021] usb 2-1: new high-speed USB device number 28 using ehci-pci Aug 16 10:59:14 localhost kernel: [661847.021290] usb 2-1: New USB device found, idVendor=1949, idProduct=0012 Aug 16 10:59:14 localhost kernel: [661847.021295] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Aug 16 10:59:14 localhost kernel: [661847.021298] usb 2-1: Product: Android Aug 16 10:59:14 localhost kernel: [661847.021300] usb 2-1: Manufacturer: Android Aug 16 10:59:14 localhost kernel: [661847.021303] usb 2-1: SerialNumber: B0850706443401A1 Which is what used to be written in 14.04 whenver I plugged in the tablet or my Samsung phone. One note when the phone is plugged in the below lines are not written to syslog just the typical information above. I've attached a file with what is written to syslog. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "fire-tablet.txt" https://bugs.launchpad.net/bugs/1613802/+attachment/4722170/+files/fire-tablet.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1613802 Title: When Amazon Fire tablet is connected via USB information on tablet is written to syslog every 15 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1613802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1405441] Re: nautilus crashes when trying to view the properties of any folder not owned by root with gksudo or sudo
On Thu, 2015-02-05 at 02:03 +, Tim wrote: chris, you need to test with the actual package in trusty (1:3.10.1-0ubuntu9.6 ), that will probably mean you need to purge the ppa or use a vm If I recall I was running the 3.12.0 version when I reported this bug. If it requires me regressing to a lower version I'd much rather someone else test this that is still running 3.10 as I've currently got too much going right now with trying to find a kernel bug, build ClamAv for some older versions and other projects. Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 20:20:53 up 9:38, 1 user, load average: 0.25, 0.33, 0.38 Ubuntu 14.04.1 LTS, kernel 3.13.0-45-generic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1405441 Title: nautilus crashes when trying to view the properties of any folder not owned by root with gksudo or sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1405441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1405441] Re: nautilus crashes when trying to view the properties of any folder not owned by root with gksudo or sudo
On Wed, 2015-02-04 at 18:16 +, Chris J Arges wrote: Hello chris, or anyone else affected, Accepted nautilus into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nautilus/1:3.10.1-0ubuntu9.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: nautilus (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu Trusty) Status: New = Fix Committed ** Tags added: verification-needed This bug has been fixed about a month ago: Start-Date: 2015-01-08 19:44:12 Commandline: aptdaemon role='role-commit-packages' sender=':1.92' Upgrade: libnautilus-extension1a:amd64 (3.12.2-0ubuntu1~trusty3, 3.12.2-0ubuntu1~trusty4), cpio:amd64 (2.11+dfsg-1ubuntu1, 2.11 +dfsg-1ubuntu1.1), nautilus:amd64 (3.12.2-0ubuntu1~trusty3, 3.12.2-0ubuntu1~trusty4), nautilus-data:amd64 (3.12.2-0ubuntu1~trusty3, 3.12.2-0ubuntu1~trusty4), nautilus-dbg:amd64 (3.12.2-0ubuntu1~trusty3, 3.12.2-0ubuntu1~trusty4) End-Date: 2015-01-08 19:45:41 Do you still wish for me to do some testing? -- Chris KeyID 0xE372A7DA98E6705C 31.11°N 97.89°W (Elev. 1092 ft) 19:20:56 up 8:38, 1 user, load average: 0.10, 0.18, 0.26 Ubuntu 14.04.1 LTS, kernel 3.13.0-45-generic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1405441 Title: nautilus crashes when trying to view the properties of any folder not owned by root with gksudo or sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1405441/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
