Pluma bug and proposed fix: Where do I report, and what happens next?

Eeqmcsq · 2024-11-03 21:49:41

I found a minor GUI bug in the pluma text editor that comes with the MATE Desktop. I downloaded the source code, compiled it, and came up with a fix that requires a small amount of refactoring in one source file.

According to the web page "How to report a bug in Devuan", since pluma is presumably not forked by Devuan, I should file this bug + proposed fix with the Debian bug tracking system.

But if I want this fix to be added to the original pluma source code, should I file the bug and proposed fix with the MATE Desktop team instead? Or will Debian pass on the fix to the MATE Desktop team?

Since this is my first time reporting a proposed fix to an open source project, I'm also curious about what happens afterwards. If the MATE Desktop team fixes the bug in their source code, would Debian get the latest source code, recompile, and distribute the fix in the current distribution? Or could Debian fix their source code in their repository, recompile, and distribute the fix? And how would Devuan pick up the fix?

* The GUI bug

If you're curious what the GUI bug is:

- Launch the pluma text editor.
- File -> Open
- The Character Encoding combo box doesn't show that anything is selected. In earlier versions of pluma (confirmed on Devuan Jessie), the combo box defaults to the first choice "Automatically Detected". Internally, the first choice IS selected, but the GUI doesn't show it.

Ron · 2024-11-03 22:52:19

The place to report it would be somewhere here: https://github.com/mate-desktop/pluma/issues

However, I noticed that the current version is 1.26.3, but the version that is in Devuan 5's repos is 1.26.0, so it may be already fixed (??). But I didn't see this particular bug mentioned anywhere on the linked page.

Last edited by Ron (2024-11-03 22:57:52)

ralph.ronnquist · 2024-11-04 01:46:26

You should also point out that as it's github, it will require a Microsoft login for rising issues, and probably then also add that noone will want that.

Altoid · 2024-11-04 12:25:35

Hello:

Ron wrote:

... Devuan 5's repos is 1.26.0, so it may be already fixed ...

The changelog file in pluma_1.26.1-2.1_amd64.deb does not seem to mention it (?):

### pluma 1.26.1

 * Translations update
 * Fix out-of-bounds write
 * Fix double activation of extensions
 * pluma-plugins-engine: fix memory leak

### pluma 1.26.0

 * Translations update
 * filebrowser-plugin: fix segfault on open-terminal action
 * update copyright to 2021
 * build: fix shebangs
 * warning: declaration of  shadows a global declaration
 * pluma: Use EXIT_SUCCESS macro instead of int value (portability)
 * help: update help for sort plugin
 * sort plugin: Port sort plugin to the new GtkSourceView api.
--- snip ---

Cannot be tested in Daedalus; GDebi won't install -> non-satisfiable dependency: gir1.2-pluma-1.0 (=1.26.1-2.1).

Best,

A.

Last edited by Altoid (2024-11-04 12:26:12)

greenjeans · 2024-11-17 21:28:06

Works in Daedulus here. And mine showing same thing as OP.

Never noticed that before, but I usually don't open files by opening pluma first, I just click on the file.

Luv me some Pluma, it's my favorite text-editor, I even use it in my Openbox installs.

Eeqmcsq · 2024-12-09 00:42:09

I finally have some free time to make some progress on this issue. Here's an update on what I've done and what I've learned about filing bugs. Perhaps someone in the future will find this info useful.

However, I noticed that the current version is 1.26.3, but the version that is in Devuan 5's repos is 1.26.0, so it may be already fixed (??).

I looked at the current pluma source code, and the file that causes this GUI bug (pluma/pluma-encodings-combo-box.c) hasn't been changed in two years. Also, reading the code, the bug definitely still exists.

https://github.com/mate-desktop/pluma/

I created a github account and reported the issue and my proposed fix and its side effects. Ideally, I should create a pull request, but I don't know how. I'll have to try that the next time I have some free time.

https://github.com/mate-desktop/pluma/issues/703

I decided to file a bug in the Debian Bug Tracking system so that there's a record that this issue has already been posted. Devuan Daedalus has a tool "reportbug" used to report bugs to Devuan or Debian. First, I had to configure the reportbug tool so it knows what sender name and email address to use, and whether to use a GUI or a console text interface.

reportbug --configure

Then I ran the tool, which launched the bug reporting GUI.

reportbug $(which pluma)

Which posted the bug here:

https://bugs.debian.org/cgi-bin/bugrepo … ug=1089560

According to the Debian bug reporting instructions, I'm supposed to file the bug with Debian first instead of going straight to the Mate repository, since it's possible that a bug could be caused by changes made by the Debian package maintainers. Oops, too late now.

One thing I don't know is how this bug can be fixed in the current Devuan Daedalus distribution. Am I supposed to create a patch? Will the Debian maintainers create a patch? If I figure this out, I'll follow up with an update. That's all for today.

Last edited by Eeqmcsq (2024-12-09 00:51:36)

The officially official Devuan Forum!

#1 2024-11-03 21:49:41

Pluma bug and proposed fix: Where do I report, and what happens next?

#2 2024-11-03 22:52:19

Re: Pluma bug and proposed fix: Where do I report, and what happens next?

#3 2024-11-04 01:46:26

Re: Pluma bug and proposed fix: Where do I report, and what happens next?

#4 2024-11-04 12:25:35

Re: Pluma bug and proposed fix: Where do I report, and what happens next?

#5 2024-11-17 21:28:06

Re: Pluma bug and proposed fix: Where do I report, and what happens next?

#6 2024-12-09 00:42:09

Re: Pluma bug and proposed fix: Where do I report, and what happens next?

Board footer