[Bug 1904933] [NEW] New install fails at 'Grub install'

2020-11-19 Thread Chris Pollock
Public bug reported: Trying to install 20.10 from USB created from ISO downloaded, install fails at 'Grub install to /dev/sda'. This happens with both Kubuntu and Ubuntu. I chose 'Something else' at the 'where to install' prompt ('Manual' for Kubuntu), as I have a 256GB GPT SSD on a Thinkpad X201

[Bug 1760227] Re: gnome-shell crashed with SIGSEGV in js::Shape::matches() from js::ShapeHasher::match() from js::detail::HashTable

2020-11-16 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760227 Title: gnome-shell crashed with SIGSEGV in js::Shape::matches() from

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-10 Thread chris pollock
This issue appears to be fixed. No problems since last Thursday. I believe it can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899036 Title: failed to build silo: failed to compile

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-09 Thread chris pollock
So far so good, no fwupd errors so far today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899036 Title: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk To manage

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-08 Thread chris pollock
Removed, I'll check logs to see if it's fixed and let you know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899036 Title: failed to build silo: failed to compile

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-08 Thread chris pollock
See attached ** Attachment added: "20.04.1 packages installed" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1899036/+attachment/5419805/+files/focalinstalled.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1899036] Re: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-08 Thread chris pollock
Nothing new, just updates as they're needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899036 Title: failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk To manage

[Bug 1899036] [NEW] failed to build silo: failed to compile /usr/share/fwupd/quirks.d/tpm.quirk

2020-10-08 Thread chris pollock
Public bug reported: lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 apt-cache policy fwupd fwupd: Installed: 1.3.11-1~focal1 Candidate: 1.3.11-1~focal1 Version table: When fwupd attempts to run this is written to my syslog: fwupd[920251]: 11:13:34:0743 FuQuirks

[Bug 1888160] [NEW] ClamAV needs updated to reflect security fixes

2020-07-19 Thread chris pollock
Public bug reported: Description: Ubuntu 18.04.4 LTS Release: 18.04 apt-cache policy clamav clamav: Installed: 0.102.3+dfsg-0ubuntu0.18.04.1 Candidate: 0.102.3+dfsg-0ubuntu0.18.04.1 The current version of ClamAV for 18.04.4 LTS is 0.102.3+dfsg- 0ubuntu0.18.04.1. The current stable version

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2020-07-06 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2020-07-03 Thread chris pollock
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

[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

2020-07-02 Thread chris pollock
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

[Bug 1878294] [NEW] ClamAV needs updated to reflect security fixes

2020-05-12 Thread chris pollock
Public bug reported: Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy clamav clamav: Installed: 0.102.2+dfsg-0ubuntu0.18.04.1 Candidate: 0.102.2+dfsg-0ubuntu0.18.04.1 The current version of ClamAV for 18.04.4 LTS is 0.102.2+dfsg- 0ubuntu0.18.04.1. The current stable

[Bug 1861534] [NEW] Spamassassin needs updated to 3.4.4 to reflect security fixes

2020-01-31 Thread chris pollock
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy spamassassin spamassassin: Installed: 3.4.2-0ubuntu0.18.04.2 Candidate: 3.4.2-0ubuntu0.18.04.2 The current version of Spamassassin is 3.4.2, the newest version, 3.4.4 fixes two

[Bug 1856248] Re: Spamassassin needs updated to reflect security fixes

2020-01-13 Thread chris pollock
Got it Seth, thanks for the explanation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856248 Title: Spamassassin needs updated to reflect security fixes To manage notifications about this bug go

[Bug 1856248] Re: Spamassassin needs updated to reflect security fixes

2020-01-13 Thread chris pollock
I received an update to Spamassassin today however it was only to apt-cache policy spamassassin spamassassin: Installed: 3.4.2-0ubuntu0.18.04.2 Candidate: 3.4.2-0ubuntu0.18.04.2 The installed version I had prior to this was 3.4.2-0ubuntu0.18.04.1. Why wasn't this updated to the current

[Bug 1856248] Re: Spamassassin needs updated to reflect security fixes

2019-12-17 Thread chris pollock
Thanks Christian, appreciate the update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856248 Title: Spamassassin needs updated to reflect security fixes To manage notifications about this bug go

[Bug 1856248] [NEW] Spamassassin needs updated to reflect security fixes

2019-12-12 Thread chris pollock
Public bug reported: lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy spamassassin spamassassin: Installed: 3.4.2-0ubuntu0.18.04.1 Candidate: 3.4.2-0ubuntu0.18.04.1 The current version of Spamassassin is 3.4.2, the newest version, 3.4.3 fixes two security

[Bug 1851063] Re: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)

2019-11-06 Thread Chris Pollock
As noted in the last comment I posted on this, I have managed to get the printer to work OK. Would it be possible to simplify/clarify somewhere what the different connections made by printers such as this are and mean? That is, when you plug this printer in, you get several 'printers' showing up

[Bug 1851063] Re: EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)

2019-11-06 Thread Chris Pollock
I have found a working combination of printer driver (from Epson) and printer definition (one plugged in it shows up about three times as different versions of the same XP-960), so this is not a 'bug'. Though I have to say that it's not immediately obviouw what is going on! -- You received this

[Bug 1851063] [NEW] EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)

2019-11-02 Thread Chris Pollock
Public bug reported: [code] chris@chris-BlackTower:~$ lsmod | grep usb btusb 57344 0 btrtl 20480 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm

[Bug 1841281] Re: ClamAV needs updated to reflect security fixes

2019-08-23 Thread chris pollock
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-12900 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-1798 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841281

[Bug 1841281] [NEW] ClamAV needs updated to reflect security fixes

2019-08-23 Thread chris pollock
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 apt-cache policy clamav clamav: Installed: 0.100.3+dfsg-0ubuntu0.18.04.1 Candidate: 0.100.3+dfsg-0ubuntu0.18.04.1 The current version of ClamAV for 18.04.3 LTS is 0.100.3+dfsg- 1ubuntu0.18.04.1.

[Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

2019-08-08 Thread chris pollock
I can verify that here as well uname -a Linux localhost 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux chris@localhost:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:

[Bug 1822503] Re: ClamAV needs updated to reflect security fixes

2019-04-03 Thread chris pollock
Thank you Marc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822503 Title: ClamAV needs updated to reflect security fixes To manage notifications about this bug go to:

[Bug 1822503] [NEW] ClamAV needs updated to reflect security fixes

2019-03-31 Thread chris pollock
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 apt-cache policy clamav clamav: Installed: 0.100.2+dfsg-1ubuntu0.18.04.1 Candidate: 0.100.2+dfsg-1ubuntu0.18.04.1 The current version of ClamAV for 18.04.2 LTS is 0.100.2+dfsg-1ubuntu0.18.04.1.

[Bug 1809505] Re: 'Livepatch-Notif' is always a zombie process after a system restart

2019-01-22 Thread chris pollock
Tested apt-cache policy update-notifier update-notifier: Installed: 3.192.1.5 Candidate: 3.192.1.5 which fixed the bug. Tag updated to reflect this. ** Tags removed: bot-comment verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this

[Bug 1809505] Re: 'Livepatch-Notif' is always a zombie process after a system restart

2018-12-29 Thread chris pollock
Question, since I have to kill the update-notifier process to get rid of the Zombie Livepatch-Notif process does this mean that updates are not being automatically checked for and that I need to run 'apt update' manually periodically? -- You received this bug notification because you are a

[Bug 1809505] Re: 'Livepatch-Notif' is always a zombie process after a system restart

2018-12-21 Thread chris pollock
Forgot to add source package when converting from question to bug. ** Package changed: ubuntu => update-notifier (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809505 Title:

[Bug 1809505] [NEW] 'Livepatch-Notif' is always a zombie process after a system restart

2018-12-21 Thread chris pollock
Public bug reported: This is Ubuntu 18.04.1 with update-notifier version apt-cache policy update-notifier update-notifier: Installed: 3.192.1.4 Candidate: 3.192.1.4 As shown here - https://imageshack.com/i/pl753Ekfp AFAICT I don't have livepatch enabled. Running: chris@localhost:/var/log$

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-11-18 Thread chris pollock
This is still on-going. New VGA cable. May happen when I start Evo, XFE, Firefox and so on but not every time. I'm attaching /var/lib/gdm3/.local/share/xorg/Xorg.0.log possibly a clue is there. I realize all these are informational (II) notations to syslog however prior to my upgrade to 18.04.1LTS

[Bug 1796863] Re: Upgrade to version 3.4.2 for Bionic

2018-11-06 Thread chris pollock
I forgot to mention that SA-Update ran with no problems also during it's normal cronjob run this afternoon. I forgot to run it after the upgrade this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1796863] Re: Upgrade to version 3.4.2 for Bionic

2018-11-06 Thread chris pollock
Package install went without a hitch. I installed each pkg individually verified the new version number spamassassin -V SpamAssassin version 3.4.2 running on Perl version 5.26.1 I also tested an email with spamassassin -D -t CVA.mbox the output is here: https://pastebin.com/sQwJchB3 Syslog

[Bug 1796863] Re: Upgrade to version 3.4.2 for Bionic

2018-10-22 Thread chris pollock
I see that 3.4.2 has been released with the just released 18.10 (Cosmic) will there also be an update for 18.04 soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796863 Title: Upgrade to version

[Bug 1796863] [NEW] Upgrade to version 3.4.2 for Bionic

2018-10-09 Thread chris pollock
Public bug reported: lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 apt-cache policy spamassassin spamassassin: Installed: 3.4.1-8build1 Candidate: 3.4.1-8build1 According to the release notes for Spamassassin 3.4.2 there have been significant bug fixes and changes

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-09-16 Thread chris pollock
I have found that starting and stopping Xfe also causes this output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II)

[Bug 1789428] Re: When expunging Evolution trash folder lots of output to syslog such as the below

2018-09-07 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu.

[Bug 1788349] Re: info directory entries missing

2018-09-05 Thread chris pollock
I'm running 18.04.1LTS updated from 16.04.5LTS. Saw this today while updating grub-common grub-pc grub-pc-bin grub2-common Processing triggers for install-info (6.5.0.dfsg.1-2) ... install-info: warning: no info dir entry in `/usr/share/info/gnash_ref.info.gz' install-info: warning: no info dir

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-09-02 Thread chris pollock
Will do Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-31 Thread chris pollock
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

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-30 Thread chris pollock
Curious as to why nothing else causes it and why even after Evo is running it will periodically write to syslog. Any other kind of testing I can do? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-30 Thread chris pollock
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

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-30 Thread chris pollock
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

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-30 Thread chris pollock
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*+

[Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-29 Thread chris pollock
** Package changed: rsyslog (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788739 Title: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset

[Bug 1788322] Re: 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

2018-08-29 Thread chris pollock
Please mark this bug as invalid. After several replies to a question at LinuxQuestions.org on this I discovered that the permissions for /var/log/cron.log were incorrect. I corrected that problem this afternoon and the reported issue has been corrected. -- You received this bug notification

[Bug 1788322] Re: 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

2018-08-28 Thread chris pollock
I've updated to version rsyslog: Installed: 8.37.0-0adiscon1bionic1 Candidate: 8.37.0-0adiscon1bionic1 via the ppa http://ppa.launchpad.net/adiscon/v8-stable/ubuntu The issue is still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1789428] [NEW] When expunging Evolution trash folder lots of output to syslog such as the below

2018-08-28 Thread chris pollock
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

[Bug 1789428] Re: When expunging Evolution trash folder lots of output to syslog such as the below

2018-08-28 Thread chris pollock
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 Bugs,

[Bug 1788322] ProcCpuinfoMinimal.txt

2018-08-25 Thread chris pollock
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1788322/+attachment/5180670/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1788322] Re: 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

2018-08-25 Thread chris pollock
apport information ** Tags added: apport-collected bionic ** Description changed: 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

[Bug 1788739] [NEW] When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-23 Thread chris pollock
Public bug reported: This started the same day I did the upgrade from 16.04LTS to 18.04LTS. Package/system information below: lsb_release -crid Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic apt-cache policy gdm3 gdm3: Installed:

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-23 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title:

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-23 Thread chris pollock
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

[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

2018-08-21 Thread chris pollock
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:

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-21 Thread chris pollock
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 Bugs,

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-21 Thread chris pollock
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 Bugs, which

Re: [Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-20 Thread chris pollock
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

[Bug 1783343] Re: package sa-compile 3.4.1-8build1 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2

2018-08-20 Thread chris pollock
As I marked this bug as affecting me I've since figured out the problem. 1. The perl module File::Scan::ClamAV was removed however it wasn't reinstalled during the upgrade. It is now installed. 2. In my case there was an issue with a non-stock SA rule, KAM.cf. This was an old version of the .cf

[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

2018-08-20 Thread chris pollock
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:

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-20 Thread chris pollock
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

[Bug 1787822] GsettingsChanges.txt

2018-08-19 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu.

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-19 Thread chris pollock
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

[Bug 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-19 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787822 Title: gnome-shell[2503]: Object

[Bug 1787822] ProcCpuinfoMinimal.txt

2018-08-19 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu.

[Bug 1787822] [NEW] gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it

2018-08-19 Thread chris pollock
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

[Bug 1783343] Re: package sa-compile 3.4.1-8build1 failed to install/upgrade: installed sa-compile package post-installation script subprocess returned error exit status 2

2018-08-16 Thread chris pollock
I experienced the same error tonight when upgrading from 16.04.5 to 18.04.1. My error code however "was installed sa-compile package post- installation script subprocess returned error exit status 13" -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1733335] Re: gnome-shell crashed with SIGABRT in meta_bug()

2018-07-20 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175 Title: gnome-shell crashed with

[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

2018-07-11 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756079 Title: gnome-shell crashed with SIGABRT: "assertion failed:

[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

2018-07-10 Thread chris pollock
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 Bugs, which is subscribed

Re: [Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-04-26 Thread chris pollock
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'

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

2018-04-26 Thread chris pollock
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

[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

2018-04-26 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616651 Title:

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-04-10 Thread chris pollock
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,

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-04-10 Thread chris pollock
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,

[Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()

2018-04-05 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749732 Title: gnome-shell crashed with SIGSEGV in

[Bug 1761635] Re: systemd-journald crashed with SIGABRT

2018-04-05 Thread chris pollock
*** This bug is a duplicate of bug 1723134 *** https://bugs.launchpad.net/bugs/1723134 Would you like to tell me why bug 1723134 does not exist? Lost something? This page does not exist, or you may not have permission to see it. If you have been to this page before, it is possible it has

[Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()

2018-04-05 Thread chris pollock
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),

[Bug 1696008] Re: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers()

2018-04-02 Thread chris pollock
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,

[Bug 1696008] Re: gnome-shell crashed with SIGSEGV in closure_invoke_notifiers()

2018-03-18 Thread chris pollock
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

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-03-16 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu.

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-03-15 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706203 Title:

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-03-15 Thread chris pollock
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

Re: [Bug 1755938] Re: gnome-shell crashed with SIGABRT in g_assertion_message()

2018-03-15 Thread chris pollock
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

[Bug 1755938] [NEW] gnome-shell crashed with SIGABRT in g_assertion_message()

2018-03-14 Thread chris pollock
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

[Bug 1733335] Re: gnome-shell crashed with SIGABRT in meta_bug()

2018-03-12 Thread chris pollock
Crash happened again this evening for no apparent reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175 Title: gnome-shell crashed with SIGABRT in meta_bug() To manage notifications about

[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

2018-02-14 Thread chris pollock
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

[Bug 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2018-01-18 Thread chris pollock
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),

[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

2017-12-08 Thread chris pollock
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 1706203] Re: gnome-shell crashed with heap corruption in g_strfreev() from g_themed_icon_finalize()

2017-10-13 Thread chris pollock
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706203 Title: gnome-shell

[Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

2017-09-15 Thread chris pollock
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

[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

2017-07-18 Thread chris pollock
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

[Bug 1705146] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size vs. prev_size: 0x0000000005405f00 ***

2017-07-18 Thread chris pollock
Thanks, however, I can't access the link you provided. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705146 Title: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': corrupted size

[Bug 924647] Re: mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip_widget()

2017-07-04 Thread chris pollock
Good idea, I'll do that the next time it occurs and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924647 Title: mail-notification crashed with SIGSEGV in

[Bug 924647] Re: mail-notification crashed with SIGSEGV in mn_mail_icon_set_tip_widget()

2017-06-28 Thread chris pollock
I keep getting this crash report periodically. According to the comment on 2012-10-04 a fix was released. Why then may I ask am I still getting this crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1678265] Re: After running ppa-purge it report apt-get update failed

2017-03-31 Thread chris pollock
On Fri, 2017-03-31 at 20:36 +, Jeremy Bicha wrote: > The problem are these two lines: > E: The repository 'http://ppa.launchpad.net/cairo-dock-team/ppa/ubunt > u xenial Release' does not have a Release file. > E: The repository 'http://ppa.launchpad.net/cairo-dock-team/weekly/ub > untu xenial

Re: [Bug 1678265] Re: After running ppa-purge it report apt-get update failed

2017-03-31 Thread chris pollock
On Fri, 2017-03-31 at 20:36 +, Jeremy Bicha wrote: > The problem are these two lines: > E: The repository 'http://ppa.launchpad.net/cairo-dock-team/ppa/ubunt > u xenial Release' does not have a Release file. > E: The repository 'http://ppa.launchpad.net/cairo-dock-team/weekly/ub > untu xenial

[Bug 1678265] Re: After running ppa-purge it report apt-get update failed

2017-03-31 Thread chris pollock
I ran these three commands which you posted to me yesterday: sudo add-apt-repository ppa:gnome3-team/gnome3-staging sudo apt update sudo ppa-purge ppa:gnome3-team/gnome3-staging I've attached all the output as a file ** Attachment added: "ppa-purge.txt"

[Bug 1678265] [NEW] After running ppa-purge it report apt-get update failed

2017-03-31 Thread chris pollock
Public bug reported: After running ppa-purge it outputs Warning: apt-get update failed for some reason - apt update has to be run manually to complete the purge. chris@localhost:~$ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 chris@localhost:~$ apt-cache policy

[Bug 1678265] Re: After running ppa-purge it report apt-get update failed

2017-03-31 Thread chris pollock
** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1678265/+attachment/4851535/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1678265

  1   2   3   4   >