Bug 20581 - Cairo-dock docklets folders cannot mount the indicated routes
Summary: Cairo-dock docklets folders cannot mount the indicated routes
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-27 08:31 CEST by Jose Manuel López
Modified: 2023-06-09 17:08 CEST (History)
1 user (show)

See Also:
Source RPM: cairo-dock-3.4.1-5.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Jose Manuel López 2017-03-27 08:31:55 CEST
Cairo-dock's docklets 

The cairo-dock docklets do not work, the folders can not mount the indicated routes, and the application stack does not.


Version-Release number of selected component (if applicable): Cairo-dock 3.4.1


How reproducible: Install the application and setup docklet folder.
Comment 1 Marja Van Waes 2017-03-27 08:51:21 CEST
Assigning to the registered maintainer.

CC: (none) => marja11
Source RPM: Cairo-dock => cairo-dock
Summary: Cairo-dock does not work properly => Cairo-dock docklets cannot mount the indicated routes
Assignee: bugsquad => shlomif

Marja Van Waes 2017-03-27 08:51:38 CEST

Summary: Cairo-dock docklets cannot mount the indicated routes => Cairo-dock docklets folders cannot mount the indicated routes

Comment 2 Jose Manuel López 2017-09-12 13:41:29 CEST
Any answer about this?

The problem continues to be reproduced.

Greetings!!

Version: Cauldron => 6

Comment 3 Jose Manuel López 2019-06-21 08:57:50 CEST
The problem continues to be reproduced in Mageia 7

Regards!!
Comment 4 Jose Manuel López 2019-07-10 10:45:22 CEST
I tried in others distributions of linux and also the bug appear.

Regards!!
Comment 5 Jose Manuel López 2019-07-10 12:39:22 CEST
I found this comment in the link: http://glx-dock.org/ww_page.php?p=Recurrents%20problems&lang=en#24-The%20dock%20doesn%27t%20launch%20the%20right%20files%20manager,%20images%20viewer,%20etc


The dock doesn't launch the right files manager, images viewer, etc.
The dock doesn't directly launch these applications, it uses GVFS to do that: e.g. if you have a problem with the files manager, you should be able to reproduce this "bug" by launching this command:
gvfs-open file:///

Gvfs links a 'mimetype' with a launcher (.desktop file): e.g. for files manager:
gvfs-mime --query inode/directory

Now you've 3 choices:

    use another application:
    mimeopen -d .
    (or edit this file: ~/.local/share/applications/mimeapps.list)
    create a new .desktop file (in ~/.local/share/applications/ ; you can find a lot of examples in /usr/share/applications/) with the command that you want to use and then use (for the files manager):
    gvfs-mime --set inode/directory your_new_launcher.desktop
    modify the .desktop file that is currently used with the command that you want to use 

If you still have this bug or if mimeopen or gvfs-mime don't work (e.g. on KDE) it's maybe because gvfs is not well supported. Please report a bug to both kde and gvfs maintainers of your distribution.
Comment 6 Lewis Smith 2019-11-28 15:31:23 CET
Re-assigning globally due to change to no specific maintainer.

Assignee: shlomif => pkg-bugs
Source RPM: cairo-dock => cairo-dock-3.4.1-5.mga7.src.rpm

Comment 7 Jose Manuel López 2020-01-02 12:19:40 CET
Is there any news about this?
Is there a development plan for this?
Has anyone been able to confirm the solution provided in comment 5?
Greetings
Comment 8 Marja Van Waes 2020-08-02 13:20:25 CEST
(In reply to Jose Manuel López from comment #7)
> Is there any news about this?
> Is there a development plan for this?
> Has anyone been able to confirm the solution provided in comment 5?
> Greetings

It seems Shlomi maintains cairo-dock again, but he maintains 4313 packages, which is way too many.

José, since you care about this package: have you ever considered becoming a Mageia packager, so you can help maintain cairo-dock?
https://wiki.mageia.org/en/Becoming_a_Mageia_Packager

Version: 6 => 7

Comment 9 Jose Manuel López 2020-08-02 19:43:37 CEST
I'll take a look at it, but I don't know if I have enough knowledge to sign part of the packing team.

Right now I'm in translators and QA, but if I can add Packers I will.

Greetings!
Comment 10 Aurelien Oudelet 2021-07-06 13:16:20 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 11 Jose Manuel López 2021-07-06 15:43:18 CEST
Hi, 

The error keeps occurring in Mageia 8, the indicated folders are not mounted.

@packager, you need to fix this for Mageia version 8 or in case the package cannot be maintained we should remove it from the repositories.

It is better that it is not available, that it is but that it does not work correctly.

I think the project is a bit abandoned.
Comment 12 Marja Van Waes 2021-07-06 16:48:13 CEST
(In reply to Jose Manuel López from comment #11)
> Hi, 
> 
> The error keeps occurring in Mageia 8, the indicated folders are not mounted.
> 
> @packager, you need to fix this for Mageia version 8 or in case the package
> cannot be maintained we should remove it from the repositories.
> 
> It is better that it is not available, that it is but that it does not work
> correctly.
> 
> I think the project is a bit abandoned.

Latest release was in 2015, so you seem to be right, but there were some commits in 2020 and 2021 https://github.com/Cairo-Dock/cairo-dock-core/commits/master/src

Version: 7 => 8

Comment 13 Jose Manuel López 2023-06-09 17:08:39 CEST
I think that we can this bug. Cairo dock is discontinued and there are more modern alternatives

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.