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.
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?
On Fri, 15 Nov 2019 07:56:55 -0500, Doug Laidlaw
<laidlaws@hotkey.net.au> 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
Maybe I should file a new report to make libatomic a dependency of Dropbox.
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 53:34:19 |
Calls: | 6,712 |
Files: | 12,243 |
Messages: | 5,355,268 |