Bug 3929

Hi, thanks for reporting this bug.
Assigned to the package maintainer.

iirc it's an upstream conf so it's more an wontfix/upstream resolution

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => juan.baptiste

>iirc it's an upstream conf so it's more an wontfix/upstream resolution

Well, then it's a recent change.  I'm pretty sure it used to be in "Tools" with the other burning apps.  I almost entered a bug report saying that k3b no longer added a menu entry, but then looked around a bit first.

Well, the .desktop file comes with the upstream tarball but we can modifiy as we wish using desktop-file-utils. This is the current categories list for k3b:


Categories=KDE;Qt;AudioVideo;DiscBurning;System;Filesystem;

and this is the list for Brasero:

Categories=GNOME;AudioVideo;DiscBurning;Core;Utility;

I could change k3b to:

Categories=KDE;Qt;AudioVideo;DiscBurning;Core;Utility;

is this ok ?

I would say no.

This change was done by upstream : https://projects.kde.org/projects/extragear/multimedia/k3b/repository/revisions/c75f83d0b79acaff37c2ebbc1123f0afd07f2857/diff/src/k3b.desktop
to fix kde #250749 https://bugs.kde.org/show_bug.cgi?id=250749

CC: (none) => balcaen.john

But brasero and k3b should appear together in the same category no matter which one it is, both are programs with the same purpose. So should brasero be moved to system tools ?

Something's wrong here.  The patch in the upstream bug should only have *added* places to find k3b to the existing set of places.  But when I examine our menus, System Tools is the *only* place k3b shows up.

The upstream bug claims that the user found k3b in Multimedia, and the developer appears to think he is adding it to System as well.  Since we don't have such categories, I think that whatever is populating our custom menus is misinterpreting the upstream Categories list --- possibly we only want to show each app in a single unique place, and System is trumping all the others ?

In any case, it appears that the problem is on our end.

Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.

Still valid.

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Still valid in cauldron.

MGA5 using XFCE both Brasero and k3b show up in Sound/Video. k3b also shows up in Tools. Looks OK to me so closed.

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