1. Forum
  2. FidoNet
  3. ALT.OS.LINUX.MAGEIA

  • Dropbox icon in Systray has started blinking

    From Maurice@2:250/1 to All on Thu Nov 21 16:12:40 2019
    Running fully-updated 64-bit Plasma Mageia-7, I have noticed recently
    that
    the Dropbox icon in Systray is blinking (slowly).
    (The SO says same happening on her Mageia-7...)

    Nevertheless Dropbox still works, and the blinking stops if I do
    'dropbox stop' then 'dropbox start -i'.

    Question is: Why has the icon started blinking?

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Thu Nov 21 16:32:52 2019
    On Thu, 21 Nov 2019 16:12:40 +0000 (UTC), Maurice wrote:
    Running fully-updated 64-bit Plasma Mageia-7, I have noticed recently
    that
    the Dropbox icon in Systray is blinking (slowly).
    (The SO says same happening on her Mageia-7...)

    Nevertheless Dropbox still works, and the blinking stops if I do
    'dropbox stop' then 'dropbox start -i'.

    Question is: Why has the icon started blinking?

    I would check status if started by systemd.

    I would hope dropbox is putting fault information in a log somewhere.

    If you have not placed your login id in the systemd-journal group
    and have logged out/in you might consider clicking up a root terminal
    and running
    journalctl | grep -i dropbox

    Nothing there, try locate -i dropbox | grep -i log


    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Werner Brinkmann@2:250/1 to All on Thu Nov 21 17:51:17 2019
    Am 21.11.19 um 17:12 schrieb Maurice:
    Running fully-updated 64-bit Plasma Mageia-7, I have noticed recently
    that
    the Dropbox icon in Systray is blinking (slowly).

    I had the same issue on my machine. Starting dropbox manually produced
    an errormessage about a missing libatomic.

    Installed libatomic and everything is well again.



    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Fri Nov 22 16:59:59 2019
    On Thu, 21 Nov 2019 18:51:17 +0100, Werner Brinkmann wrote:

    Installed libatomic and everything is well again.

    +1 here, but I wish I knew why!

    Many thanks!

    Regards,
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Fri Nov 22 17:04:21 2019
    On Thu, 21 Nov 2019 10:32:52 -0600, Bit Twister wrote:

    journalctl | grep -i dropbox

    Never-ending mass of output from June to August before I stoppede it.
    E.g.:
    Aug 04 17:29:53 pc18.mab.test dbus-daemon[8087]: [session uid=1500
    pid=8087]
    Activating service name='org.freedesktop.Notifications' requested by ':
    1.105'
    (uid=1500 pid=8359 comm="/home/mab/.dropbox-dist/dropbox-
    lnx.x86_64-78.4.11")
    Aug 04 17:29:54 pc18.mab.test kdeinit5[8131]: Registering ":1.107/org/ayatana/NotificationItem/dropbox_client_8359" to system tray
    Aug 05 11:23:11 pc18.mab.test ksmserver[8130]: org.kde.kf5.ksmserver:
    Starting
    autostart service "/home/mab/.config/autostart/dropbox.desktop" ("/usr/bin/dropbox", "start", "-i")


    ... try locate -i dropbox | grep -i log

    That showed:

    # locate -i dropbox | grep -i log
    /home/mab/dropbox-install-log
    /home/mab/.dropbox/logs
    /home/mab/.dropbox/logs/0
    /home/mab/.dropbox/logs/1
    /home/mab/.dropbox/logs/1ro
    /home/mab/.dropbox/logs/1/1-0c76-5dd6b4d6.tmp /home/mab/.dropbox/logs/1/1-83da-5dd709db /home/mab/.dropbox/logs/1/1-8e75-5dd70938 /home/mab/.dropbox/logs/1/1-d629-5dd6b4d8.tmp /home/mab/.dropbox/logs/1/~1-0ac5-5d4c13d4 /home/mab/.dropbox/logs/1ro/1-96e0-5db9d1dd.tmp /home/mab/Dropbox/Public/VBox.log /home/mab/Dropbox/Public/bootloader-rebuild-initrds-log /home/mab/Dropbox/Public/bsf4-install-log /home/mab/Dropbox/Public/cauldron-1st-update-test-netbook-log.txt /home/mab/Dropbox/Public/icons-after-login.JPG /home/mab/Dropbox/Public/plasma-urpmi.log /home/mab/Dropbox/Public/sw-update-log-9-9-14 /usr/share/icons/breeze/status/22/dropboxstatus-logo.svg /usr/share/icons/breeze-dark/status/22/dropboxstatus-logo.svg /usr/share/icons/oxygen/base/16x16/status/dropboxstatus-logo.png /usr/share/icons/oxygen/base/22x22/status/dropboxstatus-logo.png

    Regards,
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Werner Brinkmann@2:250/1 to All on Fri Nov 22 17:14:22 2019
    Am 22.11.19 um 17:59 schrieb Maurice:
    but I wish I knew why!

    As to why, see thread named "libatomic package" especially post from
    Doug Laidlow:

    Am 18.11.19 um 00:53 schrieb Doug Laidlaw:
    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.13 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 22 17:45:15 2019
    On Fri, 22 Nov 2019 17:04:21 +0000 (UTC), Maurice wrote:
    On Thu, 21 Nov 2019 10:32:52 -0600, Bit Twister wrote:

    ... try locate -i dropbox | grep -i log

    That showed:

    # locate -i dropbox | grep -i log
    /home/mab/dropbox-install-log
    /home/mab/.dropbox/logs
    /home/mab/.dropbox/logs/0
    /home/mab/.dropbox/logs/1
    /home/mab/.dropbox/logs/1ro
    /home/mab/.dropbox/logs/1/1-0c76-5dd6b4d6.tmp /home/mab/.dropbox/logs/1/1-83da-5dd709db /home/mab/.dropbox/logs/1/1-8e75-5dd70938 /home/mab/.dropbox/logs/1/1-d629-5dd6b4d8.tmp /home/mab/.dropbox/logs/1/~1-0ac5-5d4c13d4 /home/mab/.dropbox/logs/1ro/1-96e0-5db9d1dd.tmp

    Then I would have looked at /home/mab/.dropbox/logs/1*
    files for one who's date/time was closest to the
    failure.



    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Fri Nov 22 18:01:36 2019
    On Fri, 22 Nov 2019 18:14:22 +0100, Werner Brinkmann wrote:

    Doug Laidlaw said:

    Libraries are bundled with the download, and can be seen
    listed in $HOME/.dropbox-dist.

    Well, I don't see 'libatomic' in there, but strangely enough I do see in
    there 'libdrm.so.2', which has in the past caused Dropbox to segfault
    unless
    removed, but has not done that since libatomic was installed...

    Mmm, let's see how things go for a while...

    Regards,

    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Fri Nov 22 18:03:14 2019
    On Fri, 22 Nov 2019 11:45:15 -0600, Bit Twister wrote:

    Then I would have looked at /home/mab/.dropbox/logs/1*
    files for one who's date/time was closest to the failure.

    What 'failure' ?!

    Regards,
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Fri Nov 22 18:08:17 2019
    On Thu, 21 Nov 2019 18:51:17 +0100, Werner Brinkmann wrote:

    Installed libatomic and everything is well again.

    Just done DNF s/w update on my Probook's Mga7, and it complained:

    " Input error:
    libatomic.so.1: Cannot open shared object file - no such file/
    directory".

    Once that was installed, the s/w update went as normal.

    Regards,
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 22 19:27:58 2019
    On Fri, 22 Nov 2019 18:01:36 +0000 (UTC), Maurice wrote:
    On Fri, 22 Nov 2019 18:14:22 +0100, Werner Brinkmann wrote:

    Doug Laidlaw said:

    Libraries are bundled with the download, and can be seen
    listed in $HOME/.dropbox-dist.

    Well, I don't see 'libatomic' in there, but strangely enough I do see in there 'libdrm.so.2', which has in the past caused Dropbox to segfault
    unless
    removed, but has not done that since libatomic was installed...

    Mmm, let's see how things go for a while...

    If my misunderstanding is correct, Maurice description seems to indicate
    it runs for a while then starts blinking. After another start it works.
    If so all I would be able to surmise is libdrm not needed until actually
    trying to access media/file requiring the library.

    If that is the case, a command line start then media/file access should
    dump a fault message.

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Bit Twister@2:250/1 to All on Fri Nov 22 19:28:54 2019
    On Fri, 22 Nov 2019 18:03:14 +0000 (UTC), Maurice wrote:
    On Fri, 22 Nov 2019 11:45:15 -0600, Bit Twister wrote:

    Then I would have looked at /home/mab/.dropbox/logs/1*
    files for one who's date/time was closest to the failure.

    What 'failure' ?!

    When the icon starts blinking.

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Maurice@2:250/1 to All on Sat Nov 23 12:34:40 2019
    On Fri, 22 Nov 2019 13:27:58 -0600, Bit Twister wrote:

    If my misunderstanding is correct, Maurice description seems to
    indicate it runs for a while then starts blinking.

    No more blinking since libatomic installed.
    (Nor any segfaulting even though libdrm.so.2 has crept back in.)

    Regards,
    --
    /\/\aurice
    (Replace "nomail.afraid" by "bcs" to reply by email)

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: albasani.net (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Nov 26 13:07:03 2019
    On 22/11/19 4:51 am, Werner Brinkmann wrote:
    Am 21.11.19 um 17:12 schrieb Maurice:
    Running fully-updated 64-bit Plasma Mageia-7, I have noticed recently
    that
    the Dropbox icon in Systray is blinking (slowly).

    I had the same issue on my machine. Starting dropbox manually produced
    an errormessage about a missing libatomic.

    Installed libatomic and everything is well again.


    That is the issue that caused me so much grief in Bug 25701. Dropbox
    has bundled libraries in ~/.dropbox-dist/<dropbox-version> They do not include libatomic.

    I asked Dropbox to add libatomic there. Bugzilla suggested that they add libatomic to their "System Requirements." Dropbox refused to do either,
    but asked to look into my Dropbox folders instead, then gave me a
    lecture on installing dependencies. The problem is that Dropbox is not installed from an RPM, but is a direct download from the Dropbox server,
    so there is no RPM that can pull in libatomic as a dependency, and there
    is no "README.urpmi" to warn the user. There are RPMs for helpers with Dropbox, but they are a convenience only, not necessary. Apparently installing Google Chrome from a Mageia RPM will pull in libatomic, but
    this time, I didn't install Chrome.

    So, I have added libatomic to my list of packages to be installed during setup. And I gave the dropbox forum a blistering feedback.

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Nov 26 13:19:51 2019
    On 23/11/19 4:45 am, Bit Twister wrote:
    Then I would have looked at/home/mab/.dropbox/logs/1*
    files for one who's date/time was closest to the
    failure.

    But the files are in binary format. I have just looked at mine.

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: Aioe.org NNTP Server (2:250/1@fidonet)
  • From Werner Brinkmann@2:250/1 to All on Tue Nov 26 14:57:57 2019
    Am 26.11.19 um 14:07 schrieb Doug Laidlaw:
    That is the issue that caused me so much grief in Bug 25701.  Dropbox
    has bundled libraries in ~/.dropbox-dist/<dropbox-version>  They do not include libatomic.

    Thanks for explaining the situation. What I found irritating is that
    dropbox worked flawless since I set up Mageia 7 in July until some time
    this month when the Dropbox Icon startet to alternate with a Folder Icon (rather than blinking) and at the same time was obviously downloading something on every start of dropbox.

    Does that mean that dropbox was updating (or trying to update) itself automagicaly in the background and got its nickers in a twist about that libatomic dependency?

    --- MBSE BBS v1.0.7.13 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Doug Laidlaw@2:250/1 to All on Tue Nov 26 22:54:42 2019
    On 27/11/19 1:57 am, Werner Brinkmann wrote:
    Am 26.11.19 um 14:07 schrieb Doug Laidlaw:
    That is the issue that caused me so much grief in Bug 25701.  Dropbox
    has bundled libraries in ~/.dropbox-dist/<dropbox-version>  They do
    not include libatomic.

    Thanks for explaining the situation. What I found irritating is that
    dropbox worked flawless since I set up Mageia 7 in July until some time
    this month when the Dropbox Icon startet to alternate with a Folder Icon (rather than blinking) and at the same time was obviously downloading something on every start of dropbox.

    Does that mean that dropbox was updating (or trying to update) itself automagicaly in the background and got its nickers in a twist about that libatomic dependency?

    Probably. In my case, Dropbox was trying to update its version, but
    couldn't. The icon wasn't blinking; it was the same icon used when
    content is being added. I eventually ran it from the command line, and
    saw the reference to the missing dependency. Once you install the
    libatomic1 rpm, it should be OK again. Dave's comments on my previous
    thread "libatomic package" dated 15 Nov, may help.

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