Hi Osamu, thanks for your analysis.
nautilus-scripts-manager was never meant to be more than a GUI to handle these links in a comfortable way (with the possible benefit of proposing localized names if the script provides them). This is stated quite clearly in the project web page: http://www.pietrobattiston.it/nautilus-scripts-manager I myself used this package when I was a nautilus user, but I changed my default file manager some time ago. So is it an essential package? Definitely not. Is it well maintained? Probably not. But the program works regularly in bullseye; apparently something changed in bookworm and I have to understand what. The fact that it didn't get new commits since 2014 is unrelated to the issue you are experiencing. In short: if we decide to keep this package, making it work in bookworm should be a one liner, as the problematic line's aim is just to test if there is an active graphic user session. By the way: I guess you are running the program inside a graphic session? If we decide to drop this package, I don't expect too much user desperation either ;-) (mainly because of the low popcon) Cheers, Pietro Il giorno dom, 28/11/2021 alle 14.03 +0900, Osamu Aoki ha scritto: > Package: nautilus-scripts-manager > Version: 2.0-1.1 > Severity: important > X-Debbugs-Cc: Pietro Battiston <m...@pietrobattiston.it>, Piotr > Ożarowski <oza...@gmail.com>, Ondřej Nový <on...@debian.org> > > Hi, > > As I try to start nautilus-scripts-manager, it doesn't start > > $ nautilus-scripts-manager > /usr/bin/nautilus-scripts-manager:21: PyGIWarning: Pango was imported > without specifying a version first. Use gi.require_version('Pango', > '1.0') before import to ensure that the right version gets loaded. > from gi.repository import Pango, Gtk, GLib > /usr/bin/nautilus-scripts-manager:21: PyGIWarning: Gtk was imported > without specifying a version first. Use gi.require_version('Gtk', > '4.0') before import to ensure that the right version gets loaded. > from gi.repository import Pango, Gtk, GLib > Traceback (most recent call last): > File "/usr/bin/nautilus-scripts-manager", line 97, in <module> > s = Gdk.Screen.get_default() > File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", > line 32, in __getattr__ > return getattr(self._introspection_module, name) > File "/usr/lib/python3/dist-packages/gi/module.py", line 123, in > __getattr__ > raise AttributeError("%r object has no attribute %r" % ( > AttributeError: 'gi.repository.Gdk' object has no attribute 'Screen' > > > This package is not usable for the main purpose via GUI. (If we were > to use command-line, we can do it via "ln -s" anyway. I suppose > those > CLI are there for test purpose.) > > I found a salsa repository which seems to be most current and updated > some there. > https://salsa.debian.org/debian/nautilus-scripts-manager > > After making some housekeeping and a few commits, I realized the > nautilus script itself can be created and used independent of this > package and there is no Debian package using this program to manage > their nautilus scripts any more for user. > > There is a nice tutorial NautilusScriptsHowto which let us use > nautilus > script itself without this package. > https://help.ubuntu.com/community/NautilusScriptsHowto > > So I decided to stop. What is the point of keeping this package? > > I am CCing git committers of this package. > > If anyone is interested to keep this package, please update salsa > repo > and make upload. The last commit by the upstream seems to be 2014. > > If no one respond in few months, we should remove this from the next > release. > > Regards, > > Osamu > > -- System Information: > Debian Release: bookworm/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.15.0-1-amd64 (SMP w/12 CPU threads) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages nautilus-scripts-manager depends on: > ii nautilus 41.1-1 > ii python3 3.9.7-1 > ii python3-gi 3.42.0-2+b1 > > nautilus-scripts-manager recommends no packages. > > nautilus-scripts-manager suggests no packages. > > -- no debconf information
