Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n trusty/xenial/yakkety

I tried this so as to be ready for the next problem, but install does not like the armhf bit - wants amd64. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109

Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

That seems to have fixed the problem - Chromium is running as before the update. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial Date: Thu, 06 Jul

Re: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

Turned off WiFi, Chromium browser comes up with home page (google). Seems OK. Turn on WiFi, and it crashes. -- Original Message -- From: Olivier Tilloy To: rbayer...@juno.com Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109

Re: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename:xenial Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux chromium-browser: Installed:

[Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

I cannot believe I am the only one to experience this bug. Is there anything I should try which I have not yet tried? ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Converted to question:

[Bug 1702501] [NEW] chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

Public bug reported: After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got: Received signal 11 SEGV_MAPERR 0010 #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace() #1 0x7f5c4b92d80b #2 0x7f5c4bc58390 #3

[Bug 201842] [NEW] failure in Synaptic PackMan installing clamav

Public bug reported: Marked clamav for installation in synaptic package manager. Installation failed: E: clamav-base: subprocess post-installation script returned error exit status 1 E: clamav-freshclam: dependency problems - leaving unconfigured E: clamav: dependency problems - leaving

Re: [Bug 201842] Re: failure in Synaptic PackMan installing clamav

uname -a gives: Linux rohan-laptop 2.6.20-16-generic #2 SMP Tue Feb 12 05:41:34 UTC 2008 i686 GNU/Linux -- Koen Beek [EMAIL PROTECTED] wrote: Hi Rohan, could you add the output of uname -a please ? -- failure in Synaptic PackMan installing clamav https://bugs.launchpad.net/bugs/201842 You

Re: [Bug 44796] Re: [dist-upgrader] upgrade Breezy = Dapper, fails wi th No section: 'Distro' error

I don't know - I'm still running Dapper. -- Marco Rodrigues [EMAIL PROTECTED] wrote: This isn't fixed on Feisty ? -- [dist-upgrader] upgrade Breezy = Dapper, fails with No section: 'Distro' error https://bugs.launchpad.net/bugs/44796 You received this bug notification because you are a direct

[Bug 113842] error in upgrade Breezy to Dapper - no section distro

Public bug reported: Binary package hint: upgrade-system Error requested submission of /var/log/dist-upgrade.log and /var/log/dist-upgrade-apt.log Failed at end of installation, starting cleanup. (Repaired using SPM). 2007-05-09 13:49:17,354 DEBUG Foreign: skype wine 2007-05-09 13:49:17,355

Re: [Bug 113842] Re: error in upgrade Breezy to Dapper - no section di stro

It does look the same. Alas, I think the files were flushed on reboot or when I used Synaptic PM to mark the missing bits for upgrade: EncFS had a problem with libraries that had to be removed -- Josh Rhoderick [EMAIL PROTECTED] wrote: Rohan, if you don't mind, can you take a look at Bug #44796