Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

nemo-terminal python deprecated warning

Open
#560 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #571 by @dmzoneill — closed without merging
  • #572 by @dmzoneill — closed without merging

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

The warnings point to nemo-terminal-prefs.py at lines 22 and 208; inspect those Gtk.Label calls first. Launch nemo-terminal to reproduce the warnings, then verify that both PyGTKDeprecationWarning messages no longer appear.

Written by the indexing model from the issue text.

Description

Using nemo-terminal issues the following errors:

(nemo:134546): Nemo-WARNING **: 16:27:25.614: Action '90_new-launcher.nemo_action' is missing dependency: cinnamon-desktop-editor
/usr/share/nemo-terminal/nemo-terminal-prefs.py:22: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/Projects/PyGObject/InitializerDeprecations
  self.label_widget = Gtk.Label(label)

/usr/share/nemo-terminal/nemo-terminal-prefs.py:208: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/Projects/PyGObject/InitializerDeprecations
Dominant language
C
Stars
487
Forks
171
Avg merge
10d 19h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo-extensions

All issues in linuxmint/nemo-extensions

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.