Bug 21345

Summary:	Unable to remove gnome-directory-thumbnailer
Product:	Mageia	Reporter:	Bob RZ <bobzr>
Component:	RPM Packages	Assignee:	GNOME maintainers <gnome>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	olav
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Bob RZ 2017-07-25 12:16:25 CEST

Description of problem:
Seems like gnome-directory-thumbnailer is considered as an essential dependency for the gnome desktop and can't be removed without removing gnome-shell itself.

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


How reproducible:
Yes

Steps to Reproduce:
1. Try to remove gnome-directory-thumbnailer either with GUI or command line
2. Mageia needs to remove dozens of packages
3.

Rémi Verschelde 2017-07-25 13:20:40 CEST

Assignee: bugsquad => gnome

Comment 1 Olav Vitters 2017-07-26 09:49:17 CEST

There's nothing in this report that explains what you're after? What's the bug? Where is it stated that this should not be essential?

CC: (none) => olav

Comment 2 Rémi Verschelde 2017-07-26 09:56:59 CEST

Based on the French forum post [0] where I asked Bob to file a bug report, I understand that he'd like to get thumbnails for files but not for directories; but apparently the configuration options allow to enable all thumbnails (files + directories) or disable them all.

It is also claimed that in other distros (Fedora, Ubuntu) the directories are not thumbnailed, but the files are, which hints that gnome-directory-thumbnailer would be missing/optional there.

All in all I think it should reported upstream if the config option don't allow to thumbnail files while keeping plain directories with gnome-directory-thumbnailer installed - but in the meantime making the package optional seems like a working solution.

[0] https://www.mageialinux-online.org/forum/topic-23795+comment-supprimer-gnome-directory-thumbnailere.php

Comment 3 Olav Vitters 2020-04-11 12:13:48 CEST

Seems this was solved ages ago. I can easily remove it nowadays.

I cannot figure out what caused it to be required though.

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