Bug 18142

I almost closed this one as a duplicate of bug 18143

However, that one may have a different cause, there have been more problems with icons in cauldron, so keeping two separate reports for now.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs
Source RPM: Source RPM : nautilus-dropbox-1.6.2-3.mga5.nonfree.src.rpm => nautilus-dropbox-1.6.2-3.mga5

That's an upstream issue, see e.g. https://www.dropboxforum.com/hc/en-us/community/posts/205683966-Taskbar-Icon-disappeared-KDE4-Linux
Should be working if you use an older version of droboxd, or adapt the launcher as mention in the link above. I'm using an older version (dropbox-lnx.x86_64-3.14.7) and icon is showing just fine.

CC: (none) => doktor5000

dropbox stop && dbus-launch dropbox start

That worked here on Mageia-5 laptop...

> dropbox stop && dbus-launch dropbox start

> That worked here on Mageia-5 laptop...

On my Mageia-5 desktop, I simply changed the command in ~/.config/autostart from: dropbox start -i
to:   dbus-launch dropbox start i

and that works fine.

> On my Mageia-5 desktop, I simply changed the command in ~/.config/autostart 
> from: dropbox start -i
> to:   dbus-launch dropbox start i
> and that works fine.

  Also on Mageia-6-dev1!

> On my Mageia-5 desktop, I simply changed the command in ~/.config/autostart 

> from: dropbox start -i
> to:   dbus-launch dropbox start i

> and that works fine at login?

  - except I've found that after each boot that entry has somehow reverted to its original form, i.e. without the "dbus-launch" !

Is there a way to achieve 'dbus-launch dropbox start i' consistently
at login?

OK - I've managed to stabilise it in ~/.config.autostart, by using a Mageia-5 version of the .desktop file rather than re-using the Mageia-4 version.

But I hadn't realised that such files cannot be removed from that directory!
  (They appear to have gone, but are back there after the next boot.)
How does that happen?

Please have a look here: https://translate.google.cz/translate?hl=cs&sl=cs&tl=en&u=http%3A%2F%2Fforum.mageia.cz%2Findex.php%3Ftopic%3D834.msg6751%23msg6751

This is not Mageia's trouble. That's global/upstream problem.

CC: (none) => yullaw

That's interesting!  Thank you, Martin.

I am puzzled at the use of '&&' in:

    sleep 5 && dropbox stop && dbus-launch dropbox start -i 

If Dropbox is NOT running, won't the 'stop' fail, causing the 'dbus-launch...' sequence to be ignored?

Also, I would still be interested to learn the answer to the previous questions:

> is there a way to achieve 'dbus-launch dropbox start i' consistently
> at login?

> ... hadn't realised that such files cannot be removed from that directory!
              [~/.config/autostart]
>  (They appear to have gone, but are back there after the next boot.)
> How does that happen?

(In reply to Maurice Batey from comment #9)
> > is there a way to achieve 'dbus-launch dropbox start i' consistently
> > at login?
> 
> > ... hadn't realised that such files cannot be removed from that directory!
>               [~/.config/autostart]
> >  (They appear to have gone, but are back there after the next boot.)
> > How does that happen?

Dropbox create that file when it starts (even without the -i)  :)


As you people here have experience of running dropbox, I ask here before posting a bug:

Note: Cauldron

Dropbox worked including icon in mga5.
Then I updated Cauldron and icon went away.
I fixed it like this https://forums.mageia.org/en/viewtopic.php?f=15&t=10994&p=63961&hilit=dropbox#p63961  and it worked a while.

But since a couple months dropbox get SEGMENTATION FAULT when trying to launch in Plasma, while it is OK in other DE, such as Mate where it both starts and show icon.

In Plasma, it fail not only to autolaunch, but also manually from a terminal window (tried Konsole, LXTerminal, MATE Terminal - all in Plasma) :
$ dropbox start
Starting Dropbox...Done!
$ dropbox status
Dropbox isn't running!
$ .dropbox-dist/dropboxd
Segmenteringsfel (minnesutskrift skapad)   (English: Segmentation fault)

As a workaround I can while running Plasma switch screen to virtual terminal Ctrl-Alt-F2, and issue "$ dropbox start" and it starts and works OK.
There is no icon in Plasma, but i can check it runs, using "$ dropbox status".


Anyone here have an idea? How to make it not segfault at normal start in Plasma?

CC: (none) => fri

I found it was better with: 

   sleep 5 && dropbox stop && dbus-launch dropbox start i

- and got rid of the entry that had only 'dropbox start i' by dragging it into the Wastebin and emptying it.

But even then at some later boot-up *something* has restored it and messed the scheme up again...

Is there really no permanent way out of this ridiculous situation?!  :-(

Problem now gone with Mageia-6-sta2 fully updated.

(But on laptop there is still a Dropbox install problem, see:
 
     https://bugs.mageia.org/show_bug.cgi?id=20182 )

(In reply to Maurice Batey from comment #12)
> Problem now gone with Mageia-6-sta2 fully updated.
> 
> (But on laptop there is still a Dropbox install problem, see:
>  
>      https://bugs.mageia.org/show_bug.cgi?id=20182 )

Good to know, thanks :-)

Leaving this report open, though, since it was filed against Mageia 5

Using a start.sh cintaing the entry:

   dbus-launch dropbox start

the Dropbox icon always appears in the systray now. so all OK in that respect
for Mageia-5 (and also Mageia-6).

(In reply to Marja Van Waes from comment #13)
> (In reply to Maurice Batey from comment #12)
> > Problem now gone with Mageia-6-sta2 fully updated.
> > 

So this report doesn't need to stay open for Mageia 6, right? Please reopen this report and change "Version:" if I misunderstood.

Closing as OLD, since Mageia 5 is no longer supported at all.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Keywords: (none) => UPSTREAM

Agreed!