My Dropbox was unable to update and start as usual. Firstly, it looked
as though there was an update coming down, using 40% CPU, but not
getting anywhere. But that wasn't the reason.

It turned out that the libatomic package wasn't installed. The Dropbox
daemon couldn't find libatomic.so.1, and exited. I installed the
package, and the Dropbox installation already on my H.D. started and
linked to the server as normal.

I don't know if libatomic is a new dependency. I have never come across
it before. Is it perhaps part of the basic system?

Doug.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 15/11/19 11:56 pm, Doug Laidlaw wrote:

My Dropbox was unable to update and start as usual.  Firstly, it looked
as though there was an update coming down, using 40% CPU, but not
getting anywhere.  But that wasn't the reason.

It turned out that the libatomic package wasn't installed.  The Dropbox daemon couldn't find libatomic.so.1, and exited.  I installed the
package, and the Dropbox installation already on my H.D. started and
linked to the server as normal.

I don't know if libatomic is a new dependency.  I have never come across
it before. Is it perhaps part of the basic system?

Doug.

A Google search found that in other distros, Firefox and Chromium need libatomic.so.1 as well. It has been an issue since Oct 2018.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On Fri, 15 Nov 2019 07:56:55 -0500, Doug Laidlaw <[email protected]> wrote:

I don't know if libatomic is a new dependency. I have never come across
it before. Is it perhaps part of the basic system?

It's from the gcc source rpm, but not required by any Mageia 7 packages except itself. It is required by google-chrome-stable, so anyone with that installed would
already have it.

Regards, Dave Hodgins

--
Change [email protected] to [email protected] for
email replies.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 16/11/19 2:16 am, David W. Hodgins wrote:

On Fri, 15 Nov 2019 07:56:55 -0500, Doug Laidlaw
<[email protected]> wrote:

I don't know if libatomic is a new dependency.  I have never come across
it before. Is it perhaps part of the basic system?

It's from the gcc source rpm, but not required by any Mageia 7 packages except
itself. It is required by google-chrome-stable, so anyone with that installed would
already have it.

Regards, Dave Hodgins

The bug report I posted to, [Bug 25685] listed libatomic in a long list
of "gcc" rpms. It looks as though libatomic leads a separate life. I
had Google Chrome installed earlier, but my present Mga 7 is basic, and doesn't include it.

Maybe I should file a new report to make libatomic a dependency of Dropbox.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 16/11/19 5:54 pm, Doug Laidlaw wrote:

Maybe I should file a new report to make libatomic a dependency of Dropbox.

Bug report filed: Bug 25701.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)

On 17/11/19 10:14 am, Doug Laidlaw wrote:

On 16/11/19 5:54 pm, Doug Laidlaw wrote:

Maybe I should file a new report to make libatomic a dependency of
Dropbox.

Bug report filed: Bug 25701.

Mageia says: This is an "upstream" bug.The Dropbox client runs as the individual user; it doesn't need the RPM, which provides management
tools only. Libraries are bundled with the download, and can be seen
listed in $HOME/.dropbox-dist. So I have reported the bug to Dropbox.

--- MBSE BBS v1.0.7.12A (GNU/Linux-x86_64)
* Origin: Aioe.org NNTP Server (2:250/1@fidonet)